Couchbase Java Client

resubscriber IllegalArgumentException during topology changes

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.0, 1.1.1
  • Fix Version/s: 1.1.1
  • Component/s: library
  • Security Level: Public
  • Labels:
    None
  • Environment:

Description

Exception in thread "couchbase cluster resubscriber - running" java.lang.IllegalArgumentException: Bucket name cannot be null and must never be re-set to a new object.
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.subscribe(ConfigurationProviderHTTP.java:240)
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.finishResubscribe(ConfigurationProviderHTTP.java:215)
        at com.couchbase.client.CouchbaseConnectionFactory$Resubscriber.run(CouchbaseConnectionFactory.java:322)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)


Unfortunately I don't have a whole lot more insight into what's happening, but the stack trace might be helpful to examine.. assigning to myself until I have more info..
  1. File
    log2.txt.bz2
    21/Jan/13 12:48 PM
    54 kB
    Mark Nunberg
  2. File
    log2.txt.bz2
    21/Jan/13 12:48 PM
    54 kB
    Mark Nunberg
  4. Text File
    daschl-4-restart.log
    22/Jan/13 2:19 AM
    255 kB
    Michael Nitschinger
  5. Text File
    daschl-4-rebealance_two_nodes.log
    22/Jan/13 2:31 AM
    1.74 MB
    Michael Nitschinger

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael Nitschinger added a comment -
Hi Mark,

can you elaborate a bit more whats going on through the test? This particular exception can come up when the java sdk tries to subcribe to a new node when the old connection is closed. I think the scenario should give us a connection to what is happening at runtime in the java sdk.

Thanks,
Michael
Show
Michael Nitschinger added a comment - Hi Mark, can you elaborate a bit more whats going on through the test? This particular exception can come up when the java sdk tries to subcribe to a new node when the old connection is closed. I think the scenario should give us a connection to what is happening at runtime in the java sdk. Thanks, Michael
Hide
Permalink
Mark Nunberg added a comment -
I've run the Java SDKD tests several times already and cannot reproduce this. Will re-open it if i see it again
Show
Mark Nunberg added a comment - I've run the Java SDKD tests several times already and cannot reproduce this. Will re-open it if i see it again
Hide
Permalink
Mark Nunberg added a comment -
Seen again at:

http://review.couchbase.org/#/c/24092/
Show
Mark Nunberg added a comment - Seen again at: http://review.couchbase.org/#/c/24092/
Hide
Permalink
Mark Nunberg added a comment -
So as I mentioned in the bug, I closed it because I haven't seen this error. Just now, both me and Michael encountered this error while running the SDKD tests
Show
Mark Nunberg added a comment - So as I mentioned in the bug, I closed it because I haven't seen this error. Just now, both me and Michael encountered this error while running the SDKD tests
Hide
Permalink
Michael Nitschinger added a comment -
Attaching the logs for http://review.couchbase.org/#/c/24092 changeset 4 (prefixed with daschl-4-) on some test runs.

Deepti is currently running the changeset against the brun cluster, expect some info in 2 hours.
Show
Michael Nitschinger added a comment - Attaching the logs for http://review.couchbase.org/#/c/24092 changeset 4 (prefixed with daschl-4-) on some test runs. Deepti is currently running the changeset against the brun cluster, expect some info in 2 hours.
Hide
Permalink
Michael Nitschinger added a comment -
./stester -i 20devcluster.ini --service ALL --svcaction RESTART --num_nodes 3 --no_fo 1 -c failover.Once --dsw_timeres 1 -d -o restart.log -C 127.0.0.1:8050
Show
Michael Nitschinger added a comment - ./stester -i 20devcluster.ini --service ALL --svcaction RESTART --num_nodes 3 --no_fo 1 -c failover.Once --dsw_timeres 1 -d -o restart.log -C 127.0.0.1:8050
Hide
Permalink
Michael Nitschinger added a comment -
./stester -i 20devcluster.ini -c rebalance.Once --mode out --rbcount 2 --dsw_timeres 1 -d -o rebealance_two_nodes.log -C 127.0.0.1:8050
Show
Michael Nitschinger added a comment - ./stester -i 20devcluster.ini -c rebalance.Once --mode out --rbcount 2 --dsw_timeres 1 -d -o rebealance_two_nodes.log -C 127.0.0.1:8050
Hide
Permalink
Deepti Dawar added a comment -
Attaching the functional test results.
This was run against a local 2.0.0 node.
Pass rate is better this time - 92%.
Show
Deepti Dawar added a comment - Attaching the functional test results. This was run against a local 2.0.0 node. Pass rate is better this time - 92%.
Hide
Permalink
Deepti Dawar added a comment -
For the Hybrid tests - failures are still coming.

Attaching the intermittent log.
Show
Deepti Dawar added a comment - For the Hybrid tests - failures are still coming. Attaching the intermittent log.
Hide
Permalink
Deepti Dawar added a comment - - edited
The error that seems to be problematic in the unit test logs is this one -

'Timeout occurred. Please note the time in the report does not reflect the time until the timeout.
junit.framework.AssertionFailedError: Timeout occurred. Please note the time in the report does not reflect the time until the timeout.'

Most of the issues coming due to timeout.

Note : that these tests were run against a local cluster. Hence, such problems should not be occurring.
Show
Deepti Dawar added a comment - - edited The error that seems to be problematic in the unit test logs is this one - 'Timeout occurred. Please note the time in the report does not reflect the time until the timeout. junit.framework.AssertionFailedError: Timeout occurred. Please note the time in the report does not reflect the time until the timeout.' Most of the issues coming due to timeout. Note : that these tests were run against a local cluster. Hence, such problems should not be occurring.
Hide
Permalink
Michael Nitschinger added a comment -
Merged in today, right before the 1.1.1 release.
Show
Michael Nitschinger added a comment - Merged in today, right before the 1.1.1 release.

People

  • Assignee:
    Michael Nitschinger
    Reporter:
    Mark Nunberg
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: