Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
5.0.0
-
Untriaged
-
Unknown
Description
Rebalance error in ubuntu longevity against 5.0.0-3506 (RC3) - rebalances following this failed for some time and now back to normal:
017-08-31T02:12:19.155-07:00, ns_vbucket_mover:0:info:message(ns_1@172.23.106.14) - Bucket "ORDER_LINE" rebalance does not seem to be swap rebalance
|
2017-08-31T02:12:24.620-07:00, ns_vbucket_mover:0:critical:message(ns_1@172.23.106.14) - <0.277.2930> exited with {unexpected_exit,
|
{'EXIT',<0.17877.2929>,
|
{dcp_wait_for_data_move_failed,"ORDER_LINE",
|
642,'ns_1@172.23.105.62',
|
['ns_1@172.23.106.14',
|
'ns_1@172.23.106.213'],
|
{error,no_stats_for_this_vbucket}}}}
|
2017-08-31T02:12:24.622-07:00, ns_orchestrator:0:critical:message(ns_1@172.23.106.14) - Rebalance exited with reason {unexpected_exit,
|
{'EXIT',<0.17877.2929>,
|
{dcp_wait_for_data_move_failed,"ORDER_LINE",
|
642,'ns_1@172.23.105.62',
|
['ns_1@172.23.106.14','ns_1@172.23.106.213'],
|
{error,no_stats_for_this_vbucket}}}}
|
2017-08-31T02:14:10.532-07:00, ns_node_disco:4:info:node up(ns_1@172.23.99.168) - Node 'ns_1@172.23.99.168' saw that node 'ns_1@172.23.105.83' came up. Tags: []
|
2017-08-31T02:14:23.644-07:00, ns_node_disco:4:info:node up(ns_1@172.23.99.168) - Node 'ns_1@172.23.99.168' saw that node 'ns_1@172.23.105.63' came up. Tags: []
|
2017-08-31T02:14:23.849-07:00, ns_cluster:0:info:message(ns_1@172.23.106.14) - Started node add transaction by adding node 'ns_1@172.23.105.83' to nodes_wanted (group: 0)
|
2017-08-31T02:14:24.002-07:00, ns_node_disco:4:info:node up(ns_1@172.23.106.14) - Node 'ns_1@172.23.106.14' saw that node 'ns_1@172.23.105.83' came up. Tags: []
|
