spymemcached + membase + async/bulk calls do not work

[GoogleCodeExporter]

memcached-2.6rc1-36-g1a1deb9.jar 

asyncGet, asyncGetBulk, getBulk do not return expected results

I set 10 keys with values and then try the following:

ConcurrentLinkedQueue results = new ConcurrentLinkedQueue ();
for ( int i = 0; i < 10; i+\+ )
{
        results.add ( mc.asyncGet ( "e" + i ) );

}

while ( !results.isEmpty () )
{
        item = ( Future<Object> ) results.poll ();

        try{
                str = ( String ) item.get ();
        }
        catch ( InterruptedException ex ){
                Logger.getLogger ( Main.class.getName () ).log ( Level.SEVERE, null,
ex );
        }
        catch ( ExecutionException ex )
        {
                Logger.getLogger ( Main.class.getName () ).log ( Level.SEVERE, null,
ex );
        }
}

Results:

2011-04-15 17:52:19.360 WARN
net.spy.memcached.protocol.binary.OptimizedGetImpl:  Error on key e9:
I'm not responsible for this vbucket (7)
2011-04-15 17:52:19.360 WARN
net.spy.memcached.protocol.binary.OptimizedGetImpl:  Error on key e6:
I'm not responsible for this vbucket (7)
2011-04-15 17:52:19.360 WARN
net.spy.memcached.protocol.binary.OptimizedGetImpl:  Error on key e5:
I'm not responsible for this vbucket (7)

If I print out str most of the results are null. Only 2 or 3 have the correct 
value.

It seems that if there are more than one request in transit at a time we get 
the "I'm not responsible for this vbucket" errors. 

Original issue reported on code.google.com by danws6@gmail.com on 18 Apr 2011 at 2:03

[GoogleCodeExporter]

Original comment by ingen...@gmail.com on 20 Apr 2011 at 6:14

• Added labels: Milestone-Release2.7

[GoogleCodeExporter]

Original comment by ingen...@gmail.com on 23 Apr 2011 at 12:29

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by ingen...@gmail.com on 8 Jun 2011 at 10:51

• Added labels: Milestone-Release2.7.1

[GoogleCodeExporter]

I saw this issue in Spymemcached a week or two ago and submitted a fix for it. 
We will be releasing Spymemcached 2.7.1 shortly (week of 7/18/2011) and this 
version will contain a fix for this issue.

Original comment by mikewie...@gmail.com on 18 Jul 2011 at 1:01

• Changed state: Fixed

[GoogleCodeExporter]

Great, I look forward to the fix since it should be a huge performance gain for 
us.

Original comment by danws6@gmail.com on 18 Jul 2011 at 2:58