oblogproxy 无法捕获到数据变更

【 使用环境 】测试环境
【 OB CDC oblogproxy 】
【 使用版本】oblogproxy 1.0.3;ob 3.1.4;
【问题描述】
java gradle 依赖 implementation ‘com.oceanbase.logclient:logproxy-client:1.0.7’
通过 LogProxyClient 监听,只会返回 HEARTBEAT message type,无法监听到数据变更,查看oblogproxy 日志如下:

I20230215 05:18:35.401700    35 arranger.cpp:56] Handshake request from peer: file_desc:8, , msg: log_type:0, id:myClientIdyyy, ip:172.18.240.1, version:1.0.7, configuration:tb_white_list=*.*.* cluster_user=cdcuser tb_black_list=| timezone=+8:00 working_mode=storage rootserver_list=192.168.1.135:2882:2881 first_start_timestamp=0 cluster_password=B4224350F4838A0645512E7BC41160BA8087CCFC , enable_monitor:0, 
I20230215 05:18:35.401934    35 io.cpp:119] Connect to server success after poll. host=192.168.1.135,port=2881
I20230215 05:18:35.401952    35 mysql_protocol.cpp:51] Connect to server success: 192.168.1.135:2881, user: cdcuser
I20230215 05:18:35.402318    35 mysql_protocol.cpp:82] Receive handshake packet from server: 192.168.1.135:2881, user: cdcuser
I20230215 05:18:35.402357    35 ob_mysql_packet.cpp:256] Observer version: 5.7.25
I20230215 05:18:35.402379    35 ob_mysql_packet.cpp:264] Connection id: -1073464210
I20230215 05:18:35.402398    35 ob_mysql_packet.cpp:355] auth plugin name: mysql_native_password
I20230215 05:18:35.402426    35 ob_mysql_packet.cpp:593] Handshake response packet len: 83
I20230215 05:18:35.403450    35 mysql_protocol.cpp:122] Auth user success of server: 192.168.1.135:2881, user: cdcuser
I20230215 05:18:35.403475    35 mysql_protocol.cpp:214] Query obmysql SQL:show tenant
I20230215 05:18:35.445405    35 arranger.cpp:112] Client connecting: type:0, id:myClientIdyyy, ip:172.18.240.1, version:1.0.7, configuration:tb_white_list=*.*.* cluster_user=cdcuser tb_black_list=| timezone=+8:00 working_mode=storage rootserver_list=192.168.1.135:2882:2881 first_start_timestamp=0 cluster_password=B4224350F4838A0645512E7BC41160BA8087CCFC , peer:fd:8, register_time:1676438315, enable_monitor:0, packet_version:2, 
W20230215 05:18:35.445432    35 communicator.cpp:492] >>> Fork preparing, fetching lock...
W20230215 05:18:35.445458    35 communicator.cpp:494] --- Fork prepared, fetched lock
I20230215 05:18:35.445621    35 thread.cpp:41] << Joining thread: ForkThread(42)
I20230215 05:18:35.445638   682 thread.cpp:58] +++ Create thread: ForkThread(42)
I20230215 05:18:35.448350   682 source_invoke.cpp:102] +++ create oblogreader with pid: 683
I20230215 05:18:35.448860   684 thread.cpp:58] +++ Create thread: WaiterThread for pid:683(43)
I20230215 05:18:35.448901    35 thread.cpp:43] >> Joined thread: ForkThread(42)
W20230215 05:18:35.448927    35 communicator.cpp:499] <<< Fork after, unlock
I20230215 05:18:35.449010    35 communicator.cpp:231] --- Removed channel from Communicator which steal: 0, peer: file_desc:8,  flag:2
I20230215 05:18:35.449038    35 arranger.cpp:144] Client connected: myClientIdyyy
I20230215 05:18:35.449055    35 channel.cpp:49] delete Channel

看日志用的是用户cdcuser,需要确认下 cdcuser@sys 有没有监听范围内的权限。
另外在测试时,建议把working_mode置为memory。