Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
7.0.2
-
Untriaged
-
1
-
Unknown
Description
Build: 7.0.2-6531
Test: rebalance_2_nodes_during_index_building,items=60000,cluster=D,F,GROUP=P0,num_partitions=20,compare_es=True,fts_quota=990,rebalance_in=True,get-cbcollect-info=False,disable_HTP=True,get-logs=False,stop-on-failure=False,disableFileTransferRebalance=False,get-cbcollect-info=False,disable_HTP=True,get-logs=False,stop-on-failure=False,GROUP=P0,fts_quota=990,disableFileTransferRebalance=False,get-cbcollect-info=True,index_type=upside_down
File Transfer based rebalance with upside_down index failing with below and eventually falling back to old method of rebuilding the partiotion. Is this expected for upside_down index?
2021-08-20T01:15:22.849-07:00 [INFO] partition_content_receiver: copyPartitionUtil, retrying after a back off period: 2000.000000 ms for pindex: default_index_319ca4c0bf768e13_67624462
|
2021-08-20T01:15:24.105-07:00 [INFO] server_groups: no server group membership updates found for nodeDefs kind: known
|
2021-08-20T01:15:24.107-07:00 [INFO] server_groups: no server group membership updates found for nodeDefs kind: wanted
|
2021-08-20T01:15:26.851-07:00 [INFO] partition_content_receiver: copyPartitionUtil, retrying after a back off period: 4000.000000 ms for pindex: default_index_319ca4c0bf768e13_67624462
|
2021-08-20T01:15:34.853-07:00 [INFO] partition_content_receiver: copyPartitionUtil, retrying after a back off period: 8000.000000 ms for pindex: default_index_319ca4c0bf768e13_67624462
|
Logs:
https://cb-jira.s3.us-east-2.amazonaws.com/logs/rebalance/collectinfo-2021-08-20T082616-ns_1%40172.23.120.174.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/rebalance/collectinfo-2021-08-20T082616-ns_1%40172.23.96.141.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/rebalance/collectinfo-2021-08-20T082616-ns_1%40172.23.97.211.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/rebalance/collectinfo-2021-08-20T082616-ns_1%40172.23.97.212.zip