Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.1.0
-
Untriaged
-
-
Unknown
Description
Following rebalance exit seen in 5.0.1-4743 centos longevity:
2017-12-04T00:17:17.151-08:00, mb_master:0:info:message(ns_1@172.23.108.107) - Haven't heard from a higher priority node or a master, so I'm taking over.
|
2017-12-04T00:17:20.240-08:00, ns_vbucket_mover:0:critical:message(ns_1@172.23.108.103) - <0.22974.3806> exited with {unexpected_exit,
|
{'EXIT',<0.1216.3811>,
|
{{error,{badrpc,nodedown}},
|
{gen_server,call,
|
[{'janitor_agent-default',
|
'ns_1@172.23.108.107'},
|
{if_rebalance,<0.4320.3806>,
|
{update_vbucket_state,255,active,undefined,
|
undefined}},
|
infinity]}}}}
|
2017-12-04T00:17:20.249-08:00, ns_orchestrator:0:critical:message(ns_1@172.23.108.103) - Rebalance exited with reason {unexpected_exit,
|
{'EXIT',<0.1216.3811>,
|
{{error,{badrpc,nodedown}},
|
{gen_server,call,
|
[{'janitor_agent-default',
|
'ns_1@172.23.108.107'},
|
{if_rebalance,<0.4320.3806>,
|
{update_vbucket_state,255,active,
|
undefined,undefined}},
|
infinity]}}}}
|
attaching logs and screeshots
Attachments
Issue Links
- relates to
-
MB-27095 [XDCR] Service goxdcr exited with status 1 - centos longevity
- Closed