扩容binlog的时候 drainer节点启动不了

🪐 TiDB 技术问题 备份&数据迁移
1

部署的tidb是最新版，使用tiup部署的，当时部署不了解binlog，现在了解了binlog之后使用tiup扩容 但是drainer节点一直起不来这是报错：
2020-08-10T21:02:06.053+0800 DEBUG TaskFinish {“task”: “ClusterOperate: operation=StartOperation, options={Roles:[] Nodes:[192.168.0.10:8249] Force:false SSHTimeout:5 OptTimeout:120 APITimeout:300 IgnoreConfigCheck:false RetainDataRoles:[] RetainDataNodes:[]}”, “error”: “failed to start: failed to start drainer: \tdrainer 192.168.0.10:8249 failed to start: timed out waiting for port 8249 to be started after 2m0s, please check the log of the instance: timed out waiting for port 8249 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 8249 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:90\ github.com/pingcap/tiup/pkg/cluster/spec.(*instance).Ready\ \tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:121\ github.com/pingcap/tiup/pkg/cluster/operation.startInstance\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:466\ github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:502\ 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\ \tdrainer 192.168.0.10:8249 failed to start: timed out waiting for port 8249 to be started after 2m0s, please check the log of the instance\ failed to start drainer\ failed to start”}
2020-08-10T21:02:06.053+0800 INFO Execute command finished {“code”: 1, “error”: “failed to start: failed to start drainer: \tdrainer 192.168.0.10:8249 failed to start: timed out waiting for port 8249 to be started after 2m0s, please check the log of the instance: timed out waiting for port 8249 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 8249 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:90\ github.com/pingcap/tiup/pkg/cluster/spec.(*instance).Ready\ \tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:121\ github.com/pingcap/tiup/pkg/cluster/operation.startInstance\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:466\ github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:502\ 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\ \tdrainer 192.168.0.10:8249 failed to start: timed out waiting for port 8249 to be started after 2m0s, please check the log of the instance\ failed to start drainer\ failed to start”}

2

确认下 tidb 已经开启 binlog 参数，display 看下集群状态，drainer log 发出来看下

3

您好，谢谢解答，我是用tiup扩容的binlog，我直接编辑该集群的配置文件修改开启binlog参数 再重启集群可以吗？

4

哦 感谢，解决了。就是因为没有启动binlog参数。只要编辑集群的配置文件，设置了binlog启动之后，就可以了

5

ok~

6

此话题已在最后回复的 1 分钟后被自动关闭。不再允许新回复。