Uploaded image for project: 'Couchbase Java Client'
  1. Couchbase Java Client
  2. JCBC-134

resubscriber IllegalArgumentException during topology changes

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0, 1.1.1
    • Fix Version/s: 1.1.1
    • Component/s: Core
    • 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. daschl-4-rebealance_two_nodes.log
        1.74 MB
        Michael Nitschinger
      2. daschl-4-restart.log
        255 kB
        Michael Nitschinger
      3. log2.txt.bz2
        54 kB
        Mark Nunberg
      4. log2.txt.bz2
        54 kB
        Mark Nunberg
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        daschl Michael Nitschinger added a comment -

        Merged in today, right before the 1.1.1 release.

        Show
        daschl Michael Nitschinger added a comment - Merged in today, right before the 1.1.1 release.
        Hide
        deeptida 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
        deeptida 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
        deeptida Deepti Dawar added a comment -

        For the Hybrid tests - failures are still coming.

        Attaching the intermittent log.

        Show
        deeptida Deepti Dawar added a comment - For the Hybrid tests - failures are still coming. Attaching the intermittent log.
        Hide
        deeptida 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
        deeptida 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
        daschl 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
        daschl 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

          People

          • Assignee:
            daschl Michael Nitschinger
            Reporter:
            mnunberg Mark Nunberg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes