Shutdown method hangs

Alexander Khimich added a comment - 22/Feb/12 2:57 PM You could probably think that it's waiting for Queues, for async operations. But application doesn't use async operations, all calls are sync and app waits for result, to make sure data was persisted. When i do call simple client.shutdown(30, TimeUnit.SECONDS) it hangs(see bug description). When i added timeout for shutdown call, like: future = executor.submit(new Callable<Boolean>() {                                         public Boolean call() throws Exception {                         return client.shutdown(30, TimeUnit.SECONDS);                     }                 }); future.get(1, TimeUnit.MINUTES); Application able to exit with messages : WARN 22 Feb 2012 12:35:21,337 [Memcached IO over {MemcachedConnection to xxxx} - SHUTTING DOWN (waiting)] (?:?) - Closing, and reopening {QA sa=xxx, #Rops=1, #Wops=0, #iq=0, topRop=Cmd: 10 Opaque: 224540867, topWop=null, toWrite=0, interested=1}, attempt 0.  WARN 22 Feb 2012 12:35:21,339 [Memcached IO over {MemcachedConnection to xxxxx } - SHUTTING DOWN (waiting)] (?:?) - Discarding partially completed op: Cmd: 10 Opaque: 224540867 Cmd:10 it's a NoopOperationImpl Does it mean that Noop hangs?  

Alexander Khimich added a comment - 24/Feb/12 2:40 PM Another observation it happens only with spymemcached Vbucket feature http://127.0.0.1:8091/pools But doesn't happens when you use node list like 127.0.0.1:11211 127.0.0.1:11212