报错内容如下,虽然后续也会继续TiKV节点,但是不知道这里有没有继续重试修改schedule limit
,我在测试环境是直接用的–force,并不会进行transfer-leader,所以看不到效果。
如果没有增加的话,会导致升级TiKV时间变长,增加升级的变更时间。
+ [ Serial ] - UpgradeCluster
Upgrading component pd
Restarting instance 172.30.240.10:2379
Restart instance 172.30.240.10:2379 success
Restarting instance 172.30.240.4:2379
Restart instance 172.30.240.4:2379 success
Restarting instance 172.30.240.12:2379
Restart instance 172.30.240.12:2379 success
Upgrading component tikv
failed increasing schedule limit: no endpoint available, the last err was: error requesting http://172.30.240.4:2379/pd/api/v1/config, response: redirect to not leader
, code 500, ignore
Restarting instance 172.30.240.3:20160
Restart instance 172.30.240.3:20160 success