yugabyte/yugabyte-db
在 GitHub 查看[DocDB] yb-admin command may return messy results during leader blacklisting completion check
Open
#12,395 建立於 2022年5月6日
area/docdbgood first issuekind/bugpriority/medium
倉庫指標
- Star
- (8,229 star)
- PR 合併指標
- (平均合併 17天 21小時) (30 天內合併 92 個 PR)
描述
Jira Link: DB-1509
Description
Not reproduced every time, got this on master universe with following flags
instance_type='c5.xlarge',
master_gflags={
"load_balancer_max_concurrent_moves_per_table": "1",
"load_balancer_max_concurrent_moves": "1",
"ysql_num_shards_per_tserver": "50",
"yb_num_shards_per_tserver": "50",
},
tserver_gflags={
"ysql_num_shards_per_tserver": "50",
"yb_num_shards_per_tserver": "50",
}
Note that looks like 2509 is correct number, but sometimes we observe 3523 and other values. Command always evaluated on same node
yb-admin get_leader_blacklist_completion --master_addresses 172.151.27.112,172.151.31.78,172.151.29.81 2>&1
Percent complete = 48.5054 : 1292 remaining out of 2509
...
yb-admin get_leader_blacklist_completion --master_addresses 172.151.27.112,172.151.31.78,172.151.29.81 2>&1
Percent complete = 0 : 3523 remaining out of 3523
...
yb-admin get_leader_blacklist_completion --master_addresses 172.151.27.112,172.151.31.78,172.151.29.81 2>&1
Percent complete = 0 : 2509 remaining out of 2509
...
yb-admin get_leader_blacklist_completion --master_addresses 172.151.27.112,172.151.31.78,172.151.29.81 2>&1
Percent complete = 100 : 0 remaining out of 2509
Logs are to massive to be attached via GH