Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-7457

Spurious errors reported at startup of XDCR replication

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 3.0
    • Component/s: XDCR
    • Security Level: Public
    • Labels:

      Description

      Right after replication was started between two clusters, some of these messages appeared in the UI:
      2012-12-17 07:22:06 - Error replicating vbucket 250: {badmatch, {error, all_nodes_failed, <<"Failed to grab remote bucket info from any of known nodes">>}}"
      OR
      2012-12-17 07:25:52 - Error replicating vbucket 470: {http_request_failed, "HEAD", "http://Administrator:*****@10.155.240.66:8092/UserInfo%2f470%3b7b7614ca1cceb5e1940bd6ef0b30d745/", {error, {error, {eaddrinuse, [

      {lhttpc_client, send_request,1}

      ,

      {lhttpc_client, execute,9}

      ,

      {lhttpc_client, request,9}

      ]}}}}."

      They did not continue, and did not seem to affect the data transfer.

      Can they be resolved so that the customer doesn't see errors in an otherwise functioning replication?

        Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          maria Maria McDuff (Inactive) added a comment -

          MB-7786 Fixed.

          Show
          maria Maria McDuff (Inactive) added a comment - MB-7786 Fixed.
          Hide
          kzeller kzeller added a comment -

          Added to RN 2.0.1 as known issue:

          When you create a replication between two clusters, you
          may experience two incorrect error messages:
          "Failed to grab remote bucket info, vbucket" and "Error replicating vbucket X". Replication
          will start and then function as expected, but the incorrect error messages may appear
          for some time in the Web Console.
          Please ignore these two incorrect errors.

          Show
          kzeller kzeller added a comment - Added to RN 2.0.1 as known issue: When you create a replication between two clusters, you may experience two incorrect error messages: "Failed to grab remote bucket info, vbucket" and "Error replicating vbucket X". Replication will start and then function as expected, but the incorrect error messages may appear for some time in the Web Console. Please ignore these two incorrect errors.
          Hide
          dipti Dipti Borkar added a comment -

          the problem is that bucket creation is not synchronous. But yes, can we have a better message? "Remote bucket may not be ready yet"

          Show
          dipti Dipti Borkar added a comment - the problem is that bucket creation is not synchronous. But yes, can we have a better message? "Remote bucket may not be ready yet"
          Hide
          perry Perry Krug added a comment -

          Thanks Junyi, I agree with all of that. The troubling part is that the bucket was already up and ready on the cluster for at least many seconds if not minutes before the replication was created.

          Show
          perry Perry Krug added a comment - Thanks Junyi, I agree with all of that. The troubling part is that the bucket was already up and ready on the cluster for at least many seconds if not minutes before the replication was created.
          Hide
          junyi Junyi Xie (Inactive) added a comment -

          These errors usually mean either there is some network connection issue or the bucket at destination cluster is not ready yet. Once source is able to talk to the destination, we shall not see these errors. This is not serious, I understand this may cause a bit confusion at customer, but it is not clear how to determine the error should be hidden from users or not. Keep the bug open with low priority.

          Show
          junyi Junyi Xie (Inactive) added a comment - These errors usually mean either there is some network connection issue or the bucket at destination cluster is not ready yet. Once source is able to talk to the destination, we shall not see these errors. This is not serious, I understand this may cause a bit confusion at customer, but it is not clear how to determine the error should be hidden from users or not. Keep the bug open with low priority.

            People

            • Assignee:
              junyi Junyi Xie (Inactive)
              Reporter:
              perry Perry Krug
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes