[MB-7457] Spurious errors reported at startup of XDCR replication Created: 20/Dec/12  Updated: 25/Feb/14  Resolved: 20/Feb/13

Status: Closed
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: 2.0
Fix Version/s: 3.0
Security Level: Public

Type: Bug Priority: Minor
Reporter: Perry Krug Assignee: Junyi Xie (Inactive)
Resolution: Fixed Votes: 0
Labels: supportability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates MB-7786 [RN 2.0.2] Frequent replication start... Closed

 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?

 Comments   
Comment by Junyi Xie (Inactive) [ 20/Dec/12 ]
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.

Comment by Perry Krug [ 21/Dec/12 ]
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.
Comment by Dipti Borkar [ 31/Jan/13 ]
the problem is that bucket creation is not synchronous. But yes, can we have a better message? "Remote bucket may not be ready yet"
Comment by kzeller [ 15/Mar/13 ]
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.
Comment by Maria McDuff (Inactive) [ 25/Feb/14 ]
MB-7786 Fixed.
Generated at Mon Jul 14 03:58:48 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.