单节点上使用tiup cluster部署pd\tidb\tikv后，再扩容一个tiflash，报错：
2020-11-10T19:18:16.720+0800 DEBUG TaskFinish {“task”: “StartCluster”, “error”: “failed to start tiflash: \ttiflash 172.31.6.18:9543 failed to start: timed out waiting for port 9543 to be started after 2m0s, please check the log of the instance: timed out waiting for port 9543 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 9543 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\
\tgithub.com/pingcap/tiup@/pkg/cluster/module/wait_for.go:90\
github.com/pingcap/tiup/pkg/cluster/spec.PortStarted\
\tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:101\
github.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready\
\tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:132\
github.com/pingcap/tiup/pkg/cluster/operation.startInstance\
\tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:564\
github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\
\tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:679\
golang.org/x/sync/errgroup.(*Group).Go.func1\
\tgolang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57\
runtime.goexit\
\truntime/asm_amd64.s:1357\
\ttiflash 172.31.6.18:9543 failed to start: timed out waiting for port 9543 to be started after 2m0s, please check the log of the instance\
failed to start tiflash”}
./pd-ctl -u http://172.31.6.18:2379 config show 如下：
{
“replication”: {
“enable-placement-rules”: “true”,
“location-labels”: “”,
“max-replicas”: 3,
“strictly-match-label”: “false”
},
“schedule”: {
“enable-cross-table-merge”: “false”,
“enable-debug-metrics”: “false”,
“enable-location-replacement”: “true”,
“enable-make-up-replica”: “true”,
“enable-one-way-merge”: “false”,
“enable-remove-down-replica”: “true”,
“enable-remove-extra-replica”: “true”,
“enable-replace-offline-replica”: “true”,
“high-space-ratio”: 0.7,
“hot-region-cache-hits-threshold”: 3,
“hot-region-schedule-limit”: 4,
“leader-schedule-limit”: 4,
“leader-schedule-policy”: “count”,
“low-space-ratio”: 0.8,
“max-merge-region-keys”: 200000,
“max-merge-region-size”: 20,
“max-pending-peer-count”: 16,
“max-snapshot-count”: 3,
“max-store-down-time”: “30m0s”,
“merge-schedule-limit”: 8,
“patrol-region-interval”: “100ms”,
“region-schedule-limit”: 2048,
“replica-schedule-limit”: 64,
“scheduler-max-waiting-operator”: 5,
“split-merge-interval”: “1h0m0s”,
“store-limit-mode”: “manual”,
“tolerant-size-ratio”: 0
}
}
