V2 - CouchbaseCore Exception Under Rebalancing


I started abnormal testing 2.0.2 client in dev.
and I met CouchbaseCore Exception under rebalancing.

Can anybody give me help about this issue ?

JDK client version : 2.0.2
Server OS : Linux
Server Nodes : 40 (Ram Usage 30% per node)
Data Buckets : 4
Item Count

  • easter : 1,133,215,267 (571GB)
  • easter_ham : 1,170,013,272 (257GB)

2014-12-08 22:50:10,056 WARN [com.couchbase.client.core.CouchbaseCore] - Exception while Handling Response Events ResponseEvent{message=GetResponse{bucket=‘easter’, status=RETRY, cas=0, flags=0, request=GetRequest{observable=rx.subjects.AsyncSubject@68499df1, bucket=‘easter’}, content=I’m not responsible for this vbucket}, observable=rx.subjects.AsyncSubject@68499df1}, com.couchbase.client.core.CouchbaseException: Could not parse configuration

Spring context.xml


Java Code

private Map<String, JsonNode> getArgonMap(String dsids) {
final String[] dlist = dsids.split(",");
return Observable.from(dlist)
.toMap(argonKeySelector, argonValueSelector)

ArgonGather argonGather;

private final Func1<BinaryDocument, String> argonKeySelector = new Func1<BinaryDocument, String>() {
public String call(BinaryDocument binaryDocument) {
return binaryDocument.id();

private final Func1<BinaryDocument, JsonNode> argonValueSelector = new Func1<BinaryDocument, JsonNode>() {
private final ObjectMapper mapper = new ObjectMapper();

public JsonNode call(BinaryDocument binaryDocument) {
    if (binaryDocument.content() == null) {
        logger.info(String.format("argon value is null, id(%s)", binaryDocument.id()));
        return null;

    try {
        byte[] bytes = Snappy.uncompress(binaryDocument.content().array());

        return mapper.readTree(new String(bytes));
    } catch (IOException e) {
        logger.error(String.format("Snappy uncompress error, id(%s)", binaryDocument.id()), e);

    return null;


ArgonGather class

public class ArgonGather implements Func1<String, Observable<BinaryDocument>> {
    private final Logger logger = LoggerFactory.getLogger(ArgonGather.class);

    private Bucket bucket;

    private long TIMEOUT = 50L;

    public Observable<BinaryDocument> call(final String dsid) {
        return bucket.async().get(dsid, BinaryDocument.class).timeout(TIMEOUT, TimeUnit.MILLISECONDS)
                .onErrorResumeNext(new Resumer(dsid));

    class Resumer implements Func1<Throwable, Observable<? extends BinaryDocument>>{
        final private String dsid;
        public Resumer(final String dsid){
            this.dsid = dsid;

        public Observable<? extends BinaryDocument> call(Throwable throwable) {
            return bucket.async().getFromReplica(dsid, ReplicaMode.FIRST, BinaryDocument.class).timeout(TIMEOUT, TimeUnit.MILLISECONDS)

    final private Func1 empty = new Func1<Throwable, Observable<? extends BinaryDocument>>() {
        public Observable<? extends BinaryDocument> call(Throwable throwable) {
            return Observable.<BinaryDocument>empty();


Sorry … Xml code is broken.

Spring Xml

<bean id="cluster" class="com.couchbase.client.java.CouchbaseCluster" factory-method="create"
    <constructor-arg name="nodes">
        <list value-type="java.lang.String">

<bean id="bucketArg" class="com.couchbase.client.java.Bucket" factory-bean="cluster" factory-method="openBucket">
    <constructor-arg name="name" value="easter"/>
    <constructor-arg name="password" value=""/>

<bean id="bucketHam" class="com.couchbase.client.java.Bucket" factory-bean="cluster" factory-method="openBucket">
    <constructor-arg name="name" value="easter_ham"/>
    <constructor-arg name="password" value=""/>


I think this is a (known) issue, I opened a ticket for you to track here: https://www.couchbase.com/issues/browse/JVMCBC-82 we’ll have this fixed for 2.0.3, In the meantime can you use the Server 2.5 or 3.0 for your testing? I think this is affecting you with 2.2, correct?



Yes. Server 2.2.
Ok. I can use 3.0 for testing, and then let u know test results.

thx ! :smile:

Benchmarking performance of the new java client

@Sam_K perfect, keep a lookout on 2.0.3 (probably first week of january), we will have it fixed by then.

Note that if you find issues during your testing, feel free to raise issues directly here: http://www.couchbase.com/issues/browse/JCBC and we’ll work through it.