Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.0.2
-
1
Description
When FTS index definition has more number of replicas enabled than the number of FTS nodes available on the cluster, then Rebalance is always enabled even after a successful Rebalance as isBalanced field remains false because of "could not meet replication constraints"
[json_rpc:debug,2021-01-13T00:55:03.263Z,ns_1@10.112.192.103:json_rpc_connection-fts-service_api<0.4040.0>:json_rpc_connection:handle_info:94]got response: [{<<"id">>,141},
|
{<<"result">>,
|
{[{<<"rev">>,<<"MTE=">>},
|
{<<"nodes">>,[<<"6b142522436a65f3673653525da67e3c">>]},
|
{<<"isBalanced">>,false},
|
{<<"messages">>,
|
[<<"warning: resource: \"dbaNm\" -- could not meet replication constraints">>]}]}},
|
{<<"error">>,null}]
|
[json_rpc:debug,2021-01-13T00:55:03.264Z,ns_1@10.112.192.103:json_rpc_connection-fts-service_api<0.4040.0>:json_rpc_connection:handle_call:158]sending jsonrpc call:{[{jsonrpc,<<"2.0">>},
|
{id,142},
|
{method,<<"ServiceAPI.GetTaskList">>},
|
{params,[{[{rev,<<"NDM=">>},{timeout,30000}]}]}]}
|
[json_rpc:debug,2021-01-13T00:55:03.264Z,ns_1@10.112.192.103:json_rpc_connection-fts-service_api<0.4040.0>:json_rpc_connection:handle_call:158]sending jsonrpc call:{[{jsonrpc,<<"2.0">>},
|
{id,143},
|
{method,<<"ServiceAPI.GetCurrentTopology">>},
|
{params,[{[{rev,<<"MTE=">>},{timeout,30000}]}]}]}
|
Due to isBalanced = false, needs_rebalance is true for fts service and as a result Rebalance button gets enabled
{'ns_1@10.112.192.103',
|
[{last_heard,1610499377698032},
|
{now,1610499377696036},
|
{active_buckets,[]},
|
{ready_buckets,[]},
|
{status_latency,1879},
|
{outgoing_replications_safeness_level,[]},
|
{incoming_replications_conf_hashes,[]},
|
{{service_status,fts},[{connected,true},{needs_rebalance,true}]},
|
{local_tasks,[]},
|
