Details
-
Bug
-
Resolution: Fixed
-
1.6.0 beta3
-
None
-
Operating System: All
Platform: All
Description
Hi Attila!
I just pulled down your latest source, built the enyim northscale client and tried to run the following code against our Beta 3 release, which is going out the door here this evening:
{
string s = "";
using (StreamReader rdr = File.OpenText("key.txt"))
{ s = rdr.ReadToEnd(); } for (int a = 1; a < 30000; a++)
{
try
catch (Exception ec)
{
Console.WriteLine("
Set Exception caught.", ec);
}
}
string Line = Console.ReadLine();
}
Everything works beautifully, 30,000 keys are written to membase. Memcached sees all 30,000 keys come through the front end, but only 1.4K keys are actually allowed through to the engine because of vBucket errors (the server responds back “not my vBucket” for the other 28.6K keys). We’re wondering if there may be some mismatch between the hashing algorithms or in the vbucket-server mapping logic. Note that we have increased the number of vbuckets to 1024 from 256 in beta 2…though you should have picked that up from the REST interface.
There is certainly a chance I could be doing something wrong as well.
Here is my app.config as used for this simple app:
<?xml version="1.0"?>
<configuration>
<configSections>
<section name="northscale" type="NorthScale.Store.Configuration.NorthScaleClientSection, NorthScale.Store"/>
</configSections>
<northscale>
<servers bucket="default" userName="Administrator" password="j4958ph">
<add uri="http://10.1.4.253:8080/pools/default"/>
<add uri="http://10.1.4.254:8080/pools/default"/>
</servers>
<socketPool minPoolSize="10" maxPoolSize="100" connectionTimeout="00:00:10"/>
</northscale>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
</configuration>
Is there any chance we can get you the latest Beta 3 build and have you try this out?