Couchbase Server

Spurious errors reported at startup of XDCR replication

Details

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

duplicates

Improvement - An improvement or enhancement to an existing feature or task. MB-7786 [RN 2.0.2] Frequent replication start error messages "Failed to grab remote bucket info, vbucket.." at start of replication.

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Junyi Xie 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 Xie 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.
Hide
Permalink
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 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
Permalink
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 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
Permalink
Karen Zeller 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
Karen Zeller 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.

People

  • Assignee:
    Junyi Xie
    Reporter:
    Perry Krug
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: