Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
5.5.0
-
None
-
Centos 6 and centos 7
-
Untriaged
-
Centos 64-bit
-
Yes
Description
Online upgrade from 4.5.1 to vulcan .
Create 2 node cluster version 4.5.1 (23 and 232)
Create default bucket.
Create 2 vulcan nodes (234 and 29)
Add 2 vulcan nodes to 4.5.1 cluster.
Remove 2 4.5.1 nodes out (swap rebalance). Rebalance failed with error
{u'node': u'ns_1@172.23.107.234', u'code': 0, u'text': u'Rebalance exited with reason {mover_crashed,\n {unexpected_exit,\n {\'EXIT\',<0.4199.0>,\n {dcp_wait_for_data_move_failed,"default",508,\n \'ns_1@172.23.107.23\',\n [\'ns_1@172.23.107.234\',\'ns_1@172.23.107.29\'],\n {error,no_stats_for_this_vbucket}}}}}', u'shortText': u'message', u'serverTime': u'2018-04-06T16:34:24.117Z', u'module': u'ns_orchestrator', u'tstamp': 1523057664117, u'type': u'critical'}
|
[2018-04-06 16:34:34,788] - [rest_client:3132] ERROR - {u'node': u'ns_1@172.23.107.234', u'code': 0, u'text': u'<0.3973.0> exited with {unexpected_exit,\n {\'EXIT\',<0.4199.0>,\n {dcp_wait_for_data_move_failed,"default",508,\n \'ns_1@172.23.107.23\',\n [\'ns_1@172.23.107.234\',\n
|
It may relate to ticket MB-29205 since error looks the same.
Attachments
Issue Links
- duplicates
-
MB-29213 [upgrade] Rebalance failed after add vulcan nodes to 5.0.0 cluster
- Closed