He Wang

感谢反馈！之前在论坛提问的时候，支持的同学可能没搞清楚问题。我们尽快修复一下

你需要指定 obproxy 的端口，2881 端口是直连单个 observer 用的，直连的用户名不带集群名。 --- You need to specify the port of obproxy. Port 2881 is used for direct connection to a single observer. The user name for...

Thanks for the update, now we know the blocking is caused by two reasons: 1. We did not deal with empty queue. 2. The BinaryLogClient is missing LifecycleListener, or more...

Directly throwing the exception is the simplest solution, to deal with it better, you can also retry connecting for some specific exceptions, but it should not retry for all exceptions....

I think adding a server id can indeed solve the issue, and a LifecycleListener is also needed for other exceptions. Can you add a basic implementation like `ReaderThreadLifecycleListener` please?

> May be we should consider fix the BinaryLogClient with LifecycleListener in a new pr ,because another pr also should be fixed https://github.com/apache/flink-cdc/pull/1915/ +1, creating a new pr for it...

目前 OceanBase 的 Binlog 服务里只处理了 `WRITE_ROWS_EVENT = 30` ，我看了下 go-mysql 里的类型定义，应该是对应着 WRITE_ROWS_EVENTv2 的。 https://github.com/oceanbase/oblogproxy/blob/v4/src/binlog/oblogevent_type.h 您是用的哪个版本的 OceanBase 和 oblogproxy 组件，以及能确认 panic 的逻辑在 go-mysql 哪部分吗？

> 还有一个问题，obproxy 与 oblogproxy，两者有什么区别？ 因为我们这边正在试用oceanbase企业版，我不是很了解 oblogproxy 是组成 Binlog 服务的组件之一，主要做了拉取 clog 和转换 clog 为 binlog 格式文件这两件事，obproxy 也是 Binlog 服务的组件之一，它本身提供 mysql 协议的通信，通常用作流量代理，在 Binlog 服务里又多了一个解析 mysql binlog 相关命令的工作。https://www.oceanbase.com/docs/community-oblogproxy-doc-1000000001493741#1-title-%E4%BA%A7%E5%93%81%E9%A1%BB%E7%9F%A5 上面提到的 binlog 事件类型跟 oblogproxy 比较相关，不过我们其实是对...

It's weird that I can't reopen this pr.

> I cannot too, weird... @yuxiqian could you help with this case ? I have created a new pr https://github.com/apache/flink-cdc/pull/3730