After creating and opening a bucket programmatically with 2.2.4 I get hundreds of those exceptions:
WARN 2016-02-16T11:53:18,777 Slf4JLogger.warn (l. 166): Exception while Handling Request Events RequestEvent{request=null}
java.lang.IndexOutOfBoundsException: Index: 10989, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653) ~[?:1.8.0_66]
at java.util.ArrayList.get(ArrayList.java:429) ~[?:1.8.0_66]
at com.couchbase.client.core.config.DefaultCouchbaseBucketConfig.nodeIndexForMaster(DefaultCouchbaseBucketConfig.java:136) ~[core-io-1.2.4.jar:?]
at com.couchbase.client.core.node.locate.KeyValueLocator.calculateNodeId(KeyValueLocator.java:199) ~[core-io-1.2.4.jar:?]
at com.couchbase.client.core.node.locate.KeyValueLocator.locateForCouchbaseBucket(KeyValueLocator.java:159) ~[core-io-1.2.4.jar:?]
at com.couchbase.client.core.node.locate.KeyValueLocator.locate(KeyValueLocator.java:87) ~[core-io-1.2.4.jar:?]
at com.couchbase.client.core.RequestHandler.onEvent(RequestHandler.java:200) ~[core-io-1.2.4.jar:?]
at com.couchbase.client.core.RequestHandler.onEvent(RequestHandler.java:76) ~[core-io-1.2.4.jar:?]
at com.couchbase.client.deps.com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128) [core-io-1.2.4.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_66]
at com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [core-io-1.2.4.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66]
They vary in the “Index” value of the IndexOutOfBoundsException.
The code does not progress after this.
Flushing any bucket is not possible afterwards. Doing it programmatically will result in “HTTP 503”. We had to rebalance the whole cluster node by node in order to get it flushing again. But after running the code again, the symptoms reappeared.
The server is 4.0.0-4051. It does not matter if I use Java SDK 2.2.3. This issue suddenly appeared after having worked for a year before and 1 month on the CB4 cluster.