在使用tidbbinlog组件做数据同步时，pump会产生日志，但是drainer无法解析，查看drainer日志有一个不存在的drainer节点报错，好像pump没有选择往正确的drainer推送，[2024/01/24 09:57:38.813 +08:00] [ERROR] [pump.go:140] [“pump create pull binlogs client failed”] [id=esc-10-tidb4-pump-drainer:8250] [error=“rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.xx.xx.xx:8250: i/o timeout"”] [errorVerbose=“rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.xx.xx.xx:8250: i/o timeout"\ngithub.com/pingcap/errors.AddStack\n\t/go/pkg/mod/github.com/pingcap/errors@v0.11.5-0.20201029093017-5a7df2af2ac7/errors.go:174\ngithub.com/pingcap/errors.Trace\n\t/go/pkg/mod/github.com/pingcap/errors@v0.11.5-0.20201029093017-5a7df2af2ac7/juju_adaptor.go:15\ngithub.com/pingcap/tidb-binlog/drainer.(*Pump).createPullBinlogsClient\n\t/home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tidb-binlog/drainer/pump.go:238\ngithub.com/pingcap/tidb-binlog/drainer.(*Pump).PullBinlog.func1\n\t/home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tidb-binlog/drainer/pump.go:139\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357”]
有大佬遇到过这样的问题吗，不存在的drainer地址指向tiflash服务节点