Strange phenomenon occur that server tick off my client

Java SDK
1

babysitter.log write this :
2016-10-11T00:30:32.224720+08:00 WARNING 53: Slow GET operation on connection (192.168.102.83:3519 => 192.168.102.121:11210): 1317 ms"

my client write this :
2016-10-11 00:26:23,314 INFO [STDOUT] 216194298 [cb-io-1-1] INFO com.couchbase.client.core.node.Node - Disconnected from Node 192.168.102.121
2016-10-11 00:26:23,314 INFO [STDOUT] com.couchbase.client.core.RequestCancelledException: Request cancelled in-flight.
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.core.endpoint.AbstractGenericHandler.handleOutstandingOperations(AbstractGenericHandler.java:364)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.core.endpoint.AbstractGenericHandler.handlerRemoved(AbstractGenericHandler.java:345)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.callHandlerRemoved0(DefaultChannelPipeline.java:527)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.callHandlerRemoved(DefaultChannelPipeline.java:521)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.remove0(DefaultChannelPipeline.java:351)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.destroyDown(DefaultChannelPipeline.java:798)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.destroyUp(DefaultChannelPipeline.java:767)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.destroy(DefaultChannelPipeline.java:759)
2016-10-11 00:26:23,314 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline.fireChannelUnregistered(DefaultChannelPipeline.java:743)
2016-10-11 00:26:23,329 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:663)
2016-10-11 00:26:23,329 INFO [STDOUT] at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
2016-10-11 00:26:23,329 INFO [STDOUT] at com.couchbase.client.deps.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
2016-10-11 00:26:23,329 INFO [STDOUT] at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
2016-10-11 00:26:23,329 INFO [STDOUT] at com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
2016-10-11 00:26:23,329 INFO [STDOUT] at java.lang.Thread.run(Thread.java:662)

2

This looks like a server side issue, the client is printing this when a socket got closed for some reason and the operations in-flight are need to be cancelled.

Are you using full eviction?

3

No,i use value eviction,server is couchbase-4.1,client is 2.2.4

4

@drigby any idea what could have happened there?

5

I suggest you check the mcstat timings for your GET requests - most likely it took a long time to read the body of an evicted item from disk.