Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Cheshire-Cat
-
7.0.3-7031 -> 7.1.0-2335
-
Untriaged
-
1
-
No
Description
We were running system test upgrade and wanted to file a bug. Cbcollect hung on 3/31 nodes of the cluster. It was still running after 10+ hours and did not complete.
I tried to run manually to see what the issue was. See fts_cbcollect_failure.txt
for details.
FTS nodes: 
FTS cbcollect hang : 
From the cbcollect logs
fts scorch zap (/data/couchbase/@fts/good_state_5697d20623a1cd54_13aa53f3.pindex/store/00000040bd17.zap) (['cbft-bleve', 'zap', 'v11', 'footer', '/data/couchbase/@fts/good_state_5697d20623a1cd54_13aa53f3.pindex/store/00000040bd17.zap']) - Exit code 255
|
fts scorch zap (/data/couchbase/@fts/good_state_5697d20623a1cd54_13aa53f3.pindex/store/00000040975e.zap) (['cbft-bleve', 'zap', 'v11', 'footer', '/data/couchbase/@fts/good_state_5697d20623a1cd54_13aa53f3.pindex/store/00000040975e.zap']) - Exit code 255
|
fts scorch zap (/data/couchbase/@fts/good_state_5697d20623a1cd54_13aa53f3.pindex/store/000000409845.zap) (['cbft-bleve', 'zap', 'v11', 'footer', '/data/couchbase/@fts/good_state_5697d20623a1cd54_13aa53f3.pindex/store/000000409845.zap']) - Exit code 255
|
Attaching cbcollect without those 3 nodes.
Attachments
| For Gerrit Dashboard: MB-51099 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 171331,2 | MB-51099: Upgrade bleve | master | cbft | Status: MERGED | +2 | +1 |
| 171332,2 | MB-51099: Upgrade bleve | master | cbftx | Status: MERGED | +2 | +1 |
| 171333,2 | MB-51099: Upgrade bleve | master | n1fty | Status: MERGED | +2 | +1 |
| 171334,2 | MB-51099: Upgrade bleve | master | query | Status: MERGED | +2 | +1 |