Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.1.0
-
Untriaged
-
1
-
Unknown
Description
Build: 7.1.0 build 1617
- Created 4 node cluster with kv+query+index, index, seach, index+search
- Load travel-sample and beer-sample
- Created a partitioned index on beer-sample
- created fts indexes with partitions
- Enable security level to strict
- Create root ca and load node certificate with encryption for the node with kv+query+index (172.23.97.211)
One of the index test3 was stuck at 90% and after restarting fts on 172.23.120.174, it completed to 100%
Logs:
https://cb-jira.s3.us-east-2.amazonaws.com/logs/test/collectinfo-2021-11-02T082237-ns_1%40172.23.120.174.zip [Search]
https://cb-jira.s3.us-east-2.amazonaws.com/logs/test/collectinfo-2021-11-02T082237-ns_1%40172.23.96.141.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/test/collectinfo-2021-11-02T082237-ns_1%40172.23.97.211.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/test/collectinfo-2021-11-02T082237-ns_1%40172.23.97.212.zip [search and index]
Attachments
Issue Links
- relates to
-
MB-51278 [System test upgrade] - Received error on DCP stream for vb: 272, err: document exists
- Closed
-
GOCBC-1216 Missing support for status code 0x8D
- Resolved