Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.5.0
-
Security Level: Public
-
Triaged
-
No
Description
Build
4.5.0-1630
Testcase
test_24 in http://qa.sc.couchbase.com/view/FTS/job/cen006-p0-fts-vset02-00-moving-topology/
./testrunner -i INI_FILE.ini -p skip-cleanup=True,get-cbcollect-info=False,get-logs=False,stop-on-failure=False -t fts.moving_topology_fts.MovingTopFTS.node_reboot_only_kv_during_index_building,items=10000,cluster=D,F,F,GROUP=P0
Steps:
1. Create a D,F,F cluster: 1 kv node, 2 fts nodes.
2. Create a bucket, load data, create a default index.
3. Index starts building now.
4. after 10 secs, "reboot" the kv node (this may not be do-able with cluster-run).
5. After the node comes back, I observe that no new DCP connections are made, understandably indexing doesn't resume.
Attaching logs from the cluster.
https://s3.amazonaws.com/cb-customers/Aruna/collectinfo-2016-03-02T011906-ns_1%40172.23.106.139.zip <-- kv
https://s3.amazonaws.com/cb-customers/Aruna/collectinfo-2016-03-02T011906-ns_1%40172.23.106.175.zip <-- fts
https://s3.amazonaws.com/cb-customers/Aruna/collectinfo-2016-03-02T011906-ns_1%40172.23.106.176.zip <-- fts
Attachments
Issue Links
- relates to
-
MB-18517 [FTS] Indexing stuck at 99.55% following failover(hard) and add back in full recovery (of the only fts node)
- Closed