Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.6.0
-
Triaged
-
0
-
Unknown
Description
The error logging for setup_replications_failed isn't particularly clear, see example below:
[ns_server:error,2023-11-26T14:27:15.216-08:00,ns_1@172.23.107.99:replication_manager-default<0.4174.92>:dcp_replication_manager:set_desired_replications:64]Failed to setup some replications:
|
[{'ns_1@172.23.107.217',{errors,[{134,466}]}}]
|
[ns_server:info,2023-11-26T14:27:15.269-08:00,ns_1@172.23.107.217:janitor_agent-default<0.5445.92>:janitor_agent:handle_info:822]Rebalancer <35454.26524.141> die
|
d with reason {unexpected_exit,
|
{'EXIT',<35454.4286.143>,
|
{{{badmatch,
|
{error,
|
{setup_replications_failed,
|
[{'ns_1@172.23.107.217',
|
{errors,
|
[{134,466}]}}]}}},
|
...
|
The errors term is a list of tuples of mcbp status and vbucket, but it's not obvious in the log messages that that is what the numbers represent, without digging into the code manually.