Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0.1
-
Fix Version/s: 2.0.1
-
Component/s: couchbase-bucket, ns_server
-
Security Level: Public
-
Labels:
-
Environment:2.0.1-153-rel
1 bucket, Bidirectional replication between 2 clusters.
Description
- Unidirectional replication on 10M items on a 4:4 node windows cluster - Ok for 1+ day.
- Front end loads are 2k, 5k on cluster1 and cluster2.
- After some intiial replication, one of the nodes on the cluster2 is down.
Adding logs from the clusters.
- This is only xdcr test case.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Gerrit Reviews
Based on Mike's comments above and Alk's debugging that memcachd complained about enomem for requests being sent:
[couchdb:error,2013-02-15T0:59:17.950,ns_1@10.3.2.12:<0.5411.9>:couch_log:error:42]Uncaught error in HTTP request: {error,{case_clause,
}}
we may want to rerun the teest with more ram or have one of our engineers take a look at the live cluster still showing the node crash. QE please advise on this. Thanks.
CC Siri
Siri, can you suggest what QE should be looking at while running the test to discriminate between memory pressure and other causes of the timeouts. And it would be even better if we could collect this information in ns_server.
QE is going to rerun this test on EC2 cluster and see if this issue is reproducible there as well
unable to reproduce on ec2
Bulk closing all invalid bugs that are duplicate, user error, invalid. Please feel free to reopen them if you feel otherwise
Please upload the logs on both sides, also the memcached dump of the failed node at destination 10.3.2.12