Couchbase

[JCBC-162] re-enable delete observe against 2.0 server

Mon, 3 Dec 2012 14:30:52 -0600

At one point, the observe delete had been disabled on the master branch owing to changes in approach and needing to get a change merged for delete. Once this is complete, we need to revert the change.

See the review for the remove here: http://review.couchbase.org/20918

[JCBC-160] merge in changes from the release10 branch for 1.1beta

Mon, 3 Dec 2012 12:34:32 -0600

In particular, the fix for ~~JCBC-70~~ is needed, but there are a couple of changes which need to be merged in

[JCBC-158] add a debug=true option to view query options

Mon, 3 Dec 2012 01:38:08 -0600

To be able to diagnose issues that may come up with views, please add a debug=true query parameter. Optionally, we could add a cbclient.properties parameter to be able to turn on view debugging (for all view requests or just some that match a regex?) without code changes (though, with restarts).

[JCBC-157] Unsure if CouchbaseConnectionFactory.pastReconnThreshold really does what it's suppose to do

Mon, 3 Dec 2012 03:26:46 -0600

{code}
  private boolean pastReconnThreshold() {
    long currentTime = System.nanoTime();
    if (currentTime - thresholdLastCheck > 100000000) { //if longer than 10 sec
      configThresholdCount = 0; // it's been more than 10 sec since last
                                // tried, so don't try again just yet.
    }
    configThresholdCount++;
    thresholdLastCheck = currentTime;

    if (configThresholdCount >= maxConfigCheck) {
      return true;
    }
    return false;
  }
{code}

Does the above really work as expected? It looks strange. 100000000 in nanos is only 100 millis and not 10 seconds as stated in comments.
If there is more than 100 millis between calls we always reset configThresholdCount and will never return true, which seems very strange.

[JCBC-156] several javadoc warnings emitted

Mon, 3 Dec 2012 05:36:19 -0600

During build of javadoc:

  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:128: warning - @param argument "memorySize" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:143: warning - @param argument "memorySize" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:143: warning - @param argument "password" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:158: warning - @param argument "memorySize" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ViewConnection.java:199: warning - @return tag has no arguments.

[JCBC-155] add javadoc for AbstractView, View, SpatialView

Mon, 3 Dec 2012 05:36:19 -0600

When fixing up a test after a merge commit, I noted that I had to create a View object directly. In the process, I found that many of these classes are public, have public ctors, but have no javadoc. The client API takes AbstractView as an argument, so it may be tempting to just construct one. Is it correct to do so? Maybe. Javadoc doesn't tell me much.

The arguments to the ctors could also be expanded as they're a bit outside code style. Specifically, variable names should be meaningful and at least three or more characters if the variable is to be around for a while.

[JCBC-154] merge in changes from the release11c branch

Mon, 3 Dec 2012 12:34:05 -0600

When reviewing some changes on the "c" branch, I happened to notice there may be one change that hasn't been submodule merged

Upon further inspection, it looks like a few other changes haven't been merged either. We'll need to merge this branch back in.

[JCBC-153] Raise view timeout from 60s to 75s

Mon, 3 Dec 2012 05:36:19 -0600

Since the server side view timeout is 60s, we should raise the client side a bit higher. 75s seems like the right number. It should be tuneable though.

[JCBC-152] Document testing procedures for unit/functional tests

Dependency — Mon, 3 Dec 2012 05:36:19 -0600

It would be good to have clear documentation in the repo about how to:

(1) run individual tests
(2) change cluster parameters
(3) write more tests

This might be trivial or obvious to do, but very much needed.

For an example of what should be available, see:

(This does not say how to run individual tests though)
https://github.com/couchbase/libcouchbase#run-the-testsuite-towards-a-running-cluster

A more extensive example for a more complex test suite:
https://github.com/couchbase/php-ext-couchbase/blob/master/TESTING.pod

I'm marking this as a 'library' bug because this would require some detailed knowledge of how the tests are written :)

[JCBC-148] Issue with Observe API Persist.TWO and 1 dead node: Time Out when doing set operation

Mon, 3 Dec 2012 03:37:02 -0600

I have a very simple Java program that connect to the 2 nodes and do a set with the following code:

1. So I try to connect to multiple nodes
{code}
            List<URI> couchbaseServerUris = new ArrayList<URI>();
            couchbaseServerUris.add( new URI("http://192.168.0.108:8091/pools") );
            couchbaseServerUris.add( new URI("http://192.168.0.104:8091/pools") );
            CouchbaseClient client = new CouchbaseClient( couchbaseServerUris , "default" , "" );
{code}

2. Then I call the set operation
{code}

        OperationFuture<Boolean> stored = client.set( "my-dummy-key",0, "{\"name\" : \"foo\", \"title\" : \"bar-test\"}", PersistTo.TWO);
{code}

---
So everything is working as expected when the 2 nodes are up.

When I kill 1 node (for example : disconnecting, or stopping, or pausing the Ubuntu VM) I have the following behavior:

When I execute this program:
1- I have an exception saying that 1 node is down : Expected behavior (even if we could avoid a long stack trace)
{code}
2012-11-18 08:14:55.830 WARN com.couchbase.client.vbucket.ConfigurationProviderHTTP: Connection problems with URI http://192.168.0.108:8091/pools ...skipping
java.net.ConnectException: Host is down
{code}

2- When I do the set the program is stopped/blocked until it reaches a network timeout
2012-11-18 08:20:13.462 INFO com.couchbase.client.CouchbaseConnection: Shut down Couchbase client
{code}
Error while storing : Observe Timeout - Polled Unsuccessfully for at least 40 seconds.
2012-11-18 08:20:13.466 INFO done : true
done : {OperationStatus success=false: Observe Timeout - Polled Unsuccessfully for at least 40 seconds.}
com.couchbase.client.ViewNode: Couchbase I/O reactor terminated
2012-11-18 08:20:13.467 INFO com.couchbase.client.ViewNode: Couchbase I/O reactor terminated
{code}

Note that it is only happening with PersistTo.TWO
if I use PersistTo.MASTER or PersistTo.ONE : the program is executed with no error and no stop
if I use PersistTo.THREE ( or more) : the program is executed, no stop with the expected observe message : ( Error while storing : Requested persistence to 3 node(s), but only 2 are available.
)

[JCBC-147] Rename getViews() to getDesignDocument()

Dependency — Mon, 3 Dec 2012 13:39:32 -0600

The getViews() method should be renamed to getDesignDocument() before the API is stable. This is also in preparation for the createDesignDocument() and deleteDesignDocument() additions.

[JCBC-142] Observe Tests show that something is wrong in the observe impl

Mon, 3 Dec 2012 05:36:19 -0600

The newly added observe viewtests show that sometimes the full result sets are returned and sometimes not. This strongly correlates with the number of sets done in a given timeframe so I suppose the current observe implementation has a bug somewhere.

Also, the observe test inside the CouchbaseClient fails sometime which may correlate to the same issue.

[JCBC-141] Graceful Shutdown Test fails on dp4

Mon, 3 Dec 2012 05:36:20 -0600

The gracefulShutdown test on the CouchbaseClient fails.

More inspection needed before we hit a stable release!

[JCBC-139] 'delete & persist' and' delete, persist and replicate' functionalities not supported in 1.1-dp3 SDK.

Wed, 14 Nov 2012 05:58:55 -0600

couchbase-sdk-java-1.0 Manual has presented the usage specific to the 'delete & persist' and' delete, persist and replicate' functionalities but the SDK API's dont support this functionality due to an ongoing defect in the the couchbase server. Similar issue is there with the 'set and persist' and 'set and replicate' functionalities.
The manual needs to be updated accordingly.

[JCBC-136] Add support for spatial view queries

Dependency — Mon, 3 Dec 2012 05:36:20 -0600

Add support for spatial view queries

[JCBC-133] ViewFuture timeout not passed through to multiget

Tue, 6 Nov 2012 03:49:31 -0600

In the ViewFuture, the get() method accepts a timeout but it is not passed down to the mutligetRef call (which would also accept one). In this case, some operations may be stuck in there for longer than needed.

Here is a potential fix that came up:

com.couchbase.client.internal.ViewFuture.java
public ViewResponse get(long duration, TimeUnit unit)
throws InterruptedException, ExecutionException, TimeoutException {
....
Map<String, Object> docMap = multigetRef.get().get(); => Map<String, Object> docMap = multigetRef.get(duration, units);
Final ViewResponseWithDocs view = (ViewResponseWithDocs) objRef.get();
Collection<ViewRow> rows = new LinkedList<ViewRow>();
...

[JCBC-125] Don't cast view documents to strings

Mon, 3 Dec 2012 05:36:20 -0600

When objects are stored as non-strings in Couchbase and then loaded through a View, the SDK currently casts every document to a string. This works fine for JSON documents, but as soon as you want to store serialized objects it breaks.

Implicit casting is not needed in this place (see fix).

[JCBC-124] Cannot operate on keys with spaces in them

Tue, 9 Oct 2012 15:14:56 -0500

The other clients allows keys with spaces in them, such as "test key", but there is no way to operate on these using the Java client.

myclient.set("test key", 0, "test value");

java.lang.IllegalArgumentException: Key contains invalid characters: ``test key''
at net.spy.memcached.util.StringUtils.validateKey(StringUtils.java:79)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:300)
at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:733)

[JCBC-123] ArrayOutOfBounds exception during failover

Duplicate — Mon, 3 Dec 2012 05:36:20 -0600

While running a sequence of getsAsync operations, the entry point/bootstrap node is failed over. The output follows

Exception in thread "SDK Handle-8" java.lang.ArrayIndexOutOfBoundsException: -1
        at java.util.ArrayList.elementData(ArrayList.java:338)
        at java.util.ArrayList.get(ArrayList.java:351)
        at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
        at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:74)
        at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:144)
        at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
        at net.spy.memcached.MemcachedClient.asyncGets(MemcachedClient.java:888)
        at net.spy.memcached.MemcachedClient.asyncGets(MemcachedClient.java:902)
        at com.couchbase.sdkd.cbclient.GetCommandContext.doOneCommand(GetCommandContext.java:60)
        at com.couchbase.sdkd.cbclient.CommandContext.execute(CommandContext.java:266)
        at com.couchbase.sdkd.server.SdkServer.executeCommand(SdkServer.java:114)
        at com.couchbase.sdkd.server.SdkServer.handleRequest(SdkServer.java:133)
        at com.couchbase.sdkd.server.SdkServer.run(SdkServer.java:187)

[JCBC-122] Unit tests are broken

Mon, 3 Dec 2012 05:36:19 -0600

The new test admin interface that was added does not work at all for me when I try to run the unit tests. Server reports 503 errors when trying to recreate a bucket. I suspect this is because we try to do things when the bucket is not fully created yet.

[JCBC-118] Improve the docs for observe around the ReplicateTo flag

Wed, 26 Sep 2012 10:04:29 -0500

See the comment to my response of this question.

http://stackoverflow.com/questions/12521102/in-couchbases-observe-feature-what-is-the-difference-between-persistto-and/12521346#comment16856063_12521346

[JCBC-103] Java client 1.1-dp not returning documents when querying views

Tue, 9 Oct 2012 03:34:20 -0500

I'm using the Java 1.1-dp client to do queries against views. Setting query.setIncludeDocs(true) doesn't actually result in the query ViewResponse having documents (ViewRow.getDocument() returns null).

Digging into the code, it looks like that the Query class doesn't actually set the "include_docs" parameter, nor does DocsOperationImpl.parseResult try to extract the "doc" element from the returned JSON.

Is this deliberate? Or am I missing something? I'd really prefer not having to make a separate call to get the docs while iterating through a ViewResponse.

[JCBC-100] view query handling should be more reliable, have better error handling

Wed, 17 Oct 2012 14:49:09 -0500

In sections of CouchbaseClient, like asyncQueryAndIncludeDocs(), the error handling for views and queries is currently a set of assertions. This section should be more reliable, perhaps throw a checked exception from initially referencing the view and a runtime exception from queries which find views don't exist.

[JCBC-99] Java 1.1 DP exception on failed auth

Tue, 13 Nov 2012 09:07:45 -0600

Stack trace attached. Looks like a few different failures around multi-gets, there are some incomplete binary ops and failed authentications (alongside successful authentications, so I presume the user/pass is actually correct).

[JCBC-98] Multiple exceptions thrown on Shutdown()

Mon, 3 Dec 2012 05:36:19 -0600

The following exceptions are thrown when a CouchbaseClient calls shutdown()

java.io.IOException: No IO while shut down
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:201)
at com.couchbase.client.CouchbaseConnection.run(CouchbaseConnection.java:230)

This can easily be seen when logging is enabled.

[JCBC-94] Shutdown function does not shutdown ViewConnection Thread

Mon, 3 Dec 2012 05:36:20 -0600

The patch (ViewConnection.java) in the bug http://www.couchbase.com/issues/browse/JCBC-26 fixed the dead loop issue, but it introduced another Shutdown issue.
when calling the shutdown function of CouchbaseClient, it could not shutdown the thread of the ViewConnection.

Public void run() {
While(running) {
If (!reconfiguring) {
Synchronized(threadLock)
{
Boolean hasOps = false;
While(!hasOps) { ==> While(!hasOps && running)
For (viewNode node: couchNodes) {
If (node.hasWriteOps()) {
hasOps = true;
break;
}
}
......
If (!hasOps)
{
threadLock.wait();
}
}
}
If (running) {
handleIO();
}

[JCBC-92] Java error when a node is removed - need to check for pending state on a bucket

Mon, 3 Dec 2012 05:36:19 -0600

This is related to CBSE-187.

While the test was running we removed a node from the cluster, there were failures due to operation cancelled and TimeoutException and the test didn't continue.
Then we started the test again without adding back the removed node, it just threw:
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(Unknown Source)
at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:74)
at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:143)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:296)
at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:727)
<supressed>

[JCBC-91] NPE when using malformed URI

Thu, 13 Sep 2012 22:54:13 -0500

Caused by: java.lang.NullPointerException
at com.couchbase.client.CouchbaseConnectionFactory.getVBucketConfig(CouchbaseConnectionFactory.java:154)
at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:156)
at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:125)
at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:77)
at com.playtika.pool.membase.MembasePool.start(MembasePool.java:55)
... 48 more

Would prefer a more meaningful error or exception to indicate that the URI was incorrect

[JCBC-90] Views force numeric strings to be intergers

Thu, 4 Oct 2012 03:37:48 -0500

When using a view that reads a string that starts with an integer: ie date:
2012-07-30T03:26:12+00:00

From the client you are unable to request a startkey by year as it is sent as an integer in the URL request
query.setRangeStart("2000");

This will be translated as:
startkey=2000

But the request needs to be startkey="2000" for the comparison to work against a stored string.

This also causes requests for query.setRangeStart("0000"); to fail as 0000 is not a valid number.

The client should allow the developer to pick which JSON type they want to send.

[JCBC-86] Remove getHashAlgorithm and verify correct behavior of client

Mon, 3 Dec 2012 05:36:20 -0600

Current CacheConfig class has a getHashAlgorithm method and it seems to define native hash. Since there don't seem to be any uses of this, it should be removed or somehow refactored out.

[JCBC-84] We need more unit tests for views

Thu, 8 Nov 2012 04:16:10 -0600

We need more unit tests for views

[JCBC-80] Add a unit/integration test validation of OBSERVE + view stale=false

Mon, 3 Dec 2012 05:36:19 -0600

Ensure that when a synchronous set is used with the new low-level observe, the index is fully updated when querying with stale=false.

[JCBC-78] Bucket management

Fri, 14 Sep 2012 19:19:36 -0500

Add the necessary features to create and remove buckets. Also, add the ability to call the RESTful bucket flush.

[JCBC-77] Design document management, including error handling

Fri, 14 Sep 2012 19:33:57 -0500

Add the additional functionality needed to create and replace design documents. This will likely be an extension on the Bucket class.

[JCBC-66] PaginateQuery returns empty results when applying key filter

Wed, 3 Oct 2012 09:08:27 -0500

If the Query object has the "key" argument set then paginateQuery is returns empty results. It is is because of the below bug in copy() method in the Query class

public Query copy() {
    Query query = new Query();
    ........
     if (args.containsKey(KEY)) {
      query.setEndkeyDocID(((String)args.get(KEY)));
    }
   .......
}

If you look the above code it is setting setEndkeyDocID() instead of setKey(). Can this be fixed asap instead of we trying to override the functionality, please?

Remember that the view can have duplicates so it is still applicable to have filters when we use paginateQuery.

[JCBC-65] Client constructor blocks or deadlocks

Wed, 17 Apr 2013 12:28:58 -0500

I am evaluating the couchbase product and hit a brick wall immediately when running through the simple hello world example.

I have a 3 node cluster running couchbase enterprise 1.8.2 on ubuntu 10.04 64 bit VMware images. All three are running in VMWare player instances on Windows 7 64bit.

When I try to run the Main example on Windows 7 using Java6 (64 bit) the code blocks somewhere in the Client constructor. The result is the logging below.

2012-06-14 14:07:46.313 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.150:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 14:07:46.316 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.151:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 14:07:46.319 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.152:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 14:07:59.843 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@24a4e2e3
2012-06-14 14:08:52.983 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@21ec6696
2012-06-14 14:08:52.987 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@27431340

I have also tried debugging but the code blocks in the constructor at

client = new CouchbaseClient(uris, "default", "");

The program never completes.

This works fine in a Linux environment with the following output received

2012-06-14 04:58:50.693 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.150:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 04:58:50.703 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.151:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 04:58:50.708 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.152:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 04:58:50.830 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@1bc74f37
2012-06-14 04:58:50.834 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@3a21b220
2012-06-14 04:58:50.843 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@732b3d53
2012-06-14 04:58:51.135 INFO com.couchbase.client.CouchbaseConnection: Shut down Couchbase client
Set Succeeded
Synchronous Get failed
Asynchronous Get Succeeded: Hello World!

Is there a JDK for windows 7 or a configuration setting that can be used to prevent this?

[JCBC-63] add APIs for creating and deleting design documents for CBS 2.0

Dependency — Thu, 29 Nov 2012 02:58:04 -0600

There are have been several requests from users to have APIs to create and delete views from the Java (and other) SDKs.
This is a MUST have for some customers and needs to be a part of the Client SDK we release prior to Beta.

[JCBC-58] The get() function in HTTPFuture and ViewFuture contain duplicate code

Mon, 3 Dec 2012 05:36:20 -0600

See ~~JCBC-44~~ for more info.

[JCBC-46] DefaultConfigFactory attempts to create VBucket with master == -1

Duplicate — Thu, 8 Nov 2012 04:14:15 -0600

Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
        at java.util.ArrayList.get(ArrayList.java:324)
        at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
        at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:74)
        at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:140)
        at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
        at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:296)
        at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:727)
        at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:125)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)

Possible steps to reproduce:
1) populate bucket from load file
2) delete bucket
3) create new bucket with same name
4) repopulate bucket with same keys, same order, slightly different values

The -1 value looks like it is being set when the VBucket object is created. Would it make sense to check for illegal arguments in the constructor and make the object immutable, i.e. no setMaster?

[JCBC-40] paginatedQuery throws NoSuchElementException and NPE

Mon, 3 Dec 2012 05:36:19 -0600

view iteration is incomplete and throws exceptions for
groovy code:
paginator = client.paginatedQuery(view, query, n)
while (paginator.hasNext()) {
  row = paginator.next() // Exception on this line
  ...
}

java.util.NoSuchElementException
        at java.util.LinkedList$ListItr.next(LinkedList.java:698)
        at com.couchbase.client.protocol.views.Paginator.next(Paginator.java:76)
        at com.couchbase.client.protocol.views.Paginator.next(Paginator.java:35)
        at java_util_Iterator$next.call(Unknown Source)

AND

java.lang.NullPointerException
        at com.couchbase.client.protocol.views.Paginator.getNextPage(Paginator.java:93)
        at com.couchbase.client.protocol.views.Paginator.hasNext(Paginator.java:67)
        at java_util_Iterator$hasNext.call(Unknown Source)

Paginator also has a couple odd returns
1) next() can return null, but it should never return null unless lastRow is null. I don't think lastRow should ever be null.
2) getNextPage() has a return type, HttpFuture<ViewResponse>, but always returns null

[JCBC-35] Exception during reconfiguring of client

Tue, 26 Mar 2013 07:02:38 -0500

Multiple different stackstraces below also see the following right before it starts to fail:

"Node exepcted to receive data is inactive. This could be due to afailure within the cluster. Will check for updated configuration. Key without a configured node is: akey12324234"

Then it's fails a number of times and

Failed to reconfigure client, staying with previous configuration.
java.lang.IllegalArgumentException: TODO: refactor this
        at com.couchbase.client.vbucket.config.CacheConfig.getVbucketsCount(CacheConfig.java:55)
        at com.couchbase.client.vbucket.config.DefaultConfig.compareTo(DefaultConfig.java:145)
        at com.couchbase.client.vbucket.VBucketNodeLocator.updateLocator(VBucketNodeLocator.java:133)
        at com.couchbase.client.CouchbaseConnection.reconfigure(CouchbaseConnection.java:120)
        at com.couchbase.client.CouchbaseClient.reconfigure(CouchbaseClient.java:176)
        at com.couchbase.client.vbucket.ReconfigurableObserver.update(ReconfigurableObserver.java:54)
        at java.util.Observable.notifyObservers(Observable.java:142)
        at com.couchbase.client.vbucket.BucketMonitor.setBucket(BucketMonitor.java:257)
        at com.couchbase.client.vbucket.BucketMonitor.startMonitor(BucketMonitor.java:187)
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.subscribe(ConfigurationProviderHTTP.java:243)
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.finishResubscribe(ConfigurationProviderHTTP.java:215)
        at com.couchbase.client.CouchbaseConnectionFactory.checkConfigUpdate(CouchbaseConnectionFactory.java:182)
        at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:165)
        at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
        at net.spy.memcached.MemcachedClient.asyncGet(MemcachedClient.java:835)
        at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:997)

Failed to reconfigure client, staying with previous configuration.
java.lang.IllegalArgumentException: TODO: refactor this
        at com.couchbase.client.vbucket.config.CacheConfig.getVbucketsCount(CacheConfig.java:55)
        at com.couchbase.client.vbucket.config.DefaultConfig.compareTo(DefaultConfig.java:145)
        at com.couchbase.client.vbucket.VBucketNodeLocator.updateLocator(VBucketNodeLocator.java:133)
        at com.couchbase.client.CouchbaseConnection.reconfigure(CouchbaseConnection.java:120)
        at com.couchbase.client.CouchbaseClient.reconfigure(CouchbaseClient.java:176)
        at com.couchbase.client.vbucket.ReconfigurableObserver.update(ReconfigurableObserver.java:54)
        at java.util.Observable.notifyObservers(Observable.java:142)
        at com.couchbase.client.vbucket.BucketMonitor.setBucket(BucketMonitor.java:257)
        at com.couchbase.client.vbucket.BucketMonitor.replaceConfig(BucketMonitor.java:307)
        at com.couchbase.client.vbucket.BucketUpdateResponseHandler.messageReceived(BucketUpdateResponseHandler.java:81)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
        at com.couchbase.client.vbucket.BucketUpdateResponseHandler.handleUpstream(BucketUpdateResponseHandler.java:194)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:513)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:497)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:434)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340)
        at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192)
        at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
        at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)