Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
3.0
-
Security Level: Public
-
None
-
Ubuntu, 10.3.4.20X
Centos,172.23.105.XX
Description
We saw the following errors during our upgrade and system testing. But we did not find the message informative enough, as it does not tell us which bucket in particular the vbucket belongs. Although the replication restarts and replication recovers, the message does not tell us about the same. Should these be warnings or error messages since we recovered?
Examples of Error Messages
1) Errors during Offline Upgrade (2.2.0 821 --> 2.5.0 1050)
Snap-shot of the error message
2014-01-16 14:07:13 [XMem Srv] Error replicating vbucket 26: {error, {"in batch of 1 docs: flushed: 0, rejected (eexists): 0; remote memcached errors: enoent: 0, not-my-vb: 0, invalid: 0, tmp fail: 1, enomem: 0, others: 0", "Error with their keys:1 keys with etmpfail errors([<<\"Bi_V1_V2_CB34571\">>]); "}}
2014-01-16 14:07:13 [XMem Srv] Error replicating vbucket 200: {error, {"in batch of 1 docs: flushed: 0, rejected (eexists): 0; remote memcached errors: enoent: 0, not-my-vb: 0, invalid: 0, tmp fail: 1, enomem: 0, others: 0", "Error with their keys:1 keys with etmpfail errors([<<\"Bi_V1_V2_CB29425\">>]); "}}
2014-01-16 14:07:13 [Vb Rep] Error replicating vbucket 26. Please see logs for details.
2014-01-16 14:07:13 [Vb Rep] Error replicating vbucket 200. Please see logs for details.
2014-01-16 14:07:12 [XMem Srv] Error replicating vbucket 3: {error, {"in batch of 1 docs: flushed: 0, rejected (eexists): 0; remote memcached errors: enoent: 0, not-my-vb: 0, invalid: 0, tmp fail: 1, enomem: 0, others: 0", "Error with their keys:1 keys with etmpfail errors([<<\"Source55779\">>]); "}}
2014-01-16 14:07:12 [Vb Rep] Error replicating vbucket 3. Please see logs for details.
2014-01-16 14:07:12 [Vb Rep] Error replicating vbucket 294. Please see logs for details.
2014-01-16 14:07:12 [Vb Rep] Error replicating vbucket 250. Please see logs for details.
2014-01-16 14:07:12 [Vb Rep] Error replicating vbucket 190. Please see logs for details.
2014-01-16 14:07:12 [V
b Rep] Error replicating vbucket 127. Please see logs for detail
2) Errors during System Testing (2.5.0 1050)
Snap-shot of the error message
2014-01-16 14:19:5 [Vb Rep] Error replicating vbucket 408. Please see logs for details.
2014-01-16 14:19:49 [Vb Rep] Error replicating vbucket 55. Please see logs for details.
2014-01-16 14:19:49 [Vb Rep] Error replicating vbucket 541. Please see logs for details.
2014-01-16 14:19:48 [Vb Rep] Error replicating vbucket 512. Please see logs for details.
2014-01-16 14:19:47 [Vb Rep] Error replicating vbucket 816. Please see logs for details.
2014-01-16 14:19:47 [Vb Rep] Error replicating vbucket 812. Please see logs for details.
2014-01-16 14:19:47 [Vb Rep] Error replicating vbucket 779. Please see logs for details.
2014-01-16 14:19:47 [Vb Rep] Error replicating vbucket 777. Please see logs for details.
2014-01-16 14:19:47 [Vb Rep] Error replicating vbucket 776. Please see logs for details.
2014-01-16 14:19:47 [Vb Rep] Error replicating vbucket 775. Please see logs for details.
Attachments
Issue Links
- relates to
-
MB-9928 XDCR-SSL : uni-xdcr - if remote cluster's certificate changes, existing replication(s) simply stops + no clarity on how to trace the source clusters for certificate updation
- Closed