Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
3.0
-
Security Level: Public
-
None
-
Centos
3.0.0.-1107-rel
Setup:
- 2 Buckets, 1 Ddoc X 2 Views per bucket
-
Untriaged
-
Centos 64-bit
-
Unknown
Description
1. Load 120M and 177M data on the cluster
2. Reboot the cluster ( all nodes) w/ no incoming load/mutations.
- Indexing is restarted : Why do we restart indexing?
- Indexing is stuck on ddoc2
Seeing the mutation timeouts
[couchdb:error,2014-08-06T15:26:26.900,ns_1@10.6.2.164:<0.2181.0>:couch_log:error:44]dcp client (saslbucket, mapreduce_view: saslbucket _design/ddoc2 (prod/replica)): Obtaining mutation from server timed out after 60.0 seconds [RequestId 170, PartId 171, StartSeq 0, EndSeq 316375]. Waiting...
[couchdb:error,2014-08-06T15:27:26.895,ns_1@10.6.2.164:<0.2161.0>:couch_log:error:44]dcp client (saslbucket, mapreduce_view: saslbucket _design/ddoc2 (prod/main)): Obtaining mutation from server timed out after 60.0 seconds [RequestId 171, PartId 0, StartSeq 0, EndSeq 316054]. Waiting...
[couchdb:error,2014-08-06T15:27:26.901,ns_1@10.6.2.164:<0.2181.0>:couch_log:error:44]dcp client (saslbucket, mapreduce_view: saslbucket _design/ddoc2 (prod/replica)): Obtaining mutation from server timed out after 60.0 seconds [RequestId 170, PartId 171, StartSeq 0, EndSeq 316375]. Waiting...
Attaching logs