oblogproxy部署好后，binLog文件没有追加

OceanBase
#1

【 使用环境 】生产环境
【 OB or 其他组件 】OB、oblogProxy
【 使用版本 】4.2.2.0-CE
【问题描述】
已经按照文档部署oblogProxy服务
https://www.oceanbase.com/docs/community-oblogproxy-doc-1000000000861457

但是show binary logs。显示binlog文件大小一直为0.

执行： show master status; 结果如下:
image

连接obproxyLog查看logproxy状态：

image
image695×581 10 KB

#3

试试进行一些修改操作后再看看，没修改的时候是没有日志产生的。

#4

一直有大批量的数据修改

#5

/usr/local/oblogproxy/run/集群名/租户名/log下的日志是否有异常，也可以日志提供下。

#6

image
image870×239 6.87 KB

过滤ERROR发现一直有这个报错
image
image1875×573 71.6 KB

追踪整个TRACEID日志截图

image
image1893×904 115 KB

#7

CREATE BINLOG FOR TENANT PRD_OBcluster.test TO USER root PASSWORD 123456 WITH CLUSTER URL http://ip:8080/services?Action=ObRootServiceInfo&User_ID=alibaba&UID=ocpmaster&ObRegion=PRD_OBcluster;
需要先这样去启动binlog吧

#8

已经创建了binlog服务。 不然上面的日志都没有

#11

start lsn locate fail 这个报错一般是启动位点的日志被回收了，重新指定一个起点创建 binlog 试试，

查询起始时间可以参考这里的 sql OceanBase分布式数据库-海量数据 笔笔算数

#12

按你的做法，重新创建binLog服务，也没用。
我之前创建binlog服务，没有指定时间。 默认是用的当前时间位点。

[2024-07-17 20:27:54.008672] EDIAG [TLOG.FETCHER] locate_lsn_ (ob_log_ls_fetch_ctx.cpp:933) [31701][][T0][Y7B5AAC1692C9-0000000000000001-0-0] [lt=8][errcode=0] start lsn locate fail(start_lsn_locate_req={state:2, tls_id:{tenant_id:1006, ls_id:{id:1}}, start_tstamp_ns:1721190747782967000, svr_cnt:3, svr_list_consumed:3, result_svr_list_idx:-1, cur_max_start_lsn:{lsn:18446744073709551615}, cur_max_start_log_tstamp:-1, succ_locate_count:0, svr_list:[{svr:“172.26.49.127:2882”, rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y7B5AAC1692C9-00000000005000CC-0-0}, {svr:“172.22.146.197:2882”, rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y7B5AAC1692C9-00000000006000CC-0-0}, {svr:“172.30.224.165:2882”, rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y7B5AAC1692C9-00000000007000CC-0-0}], fetching_mode:“Integrated Fetching Mode”, archive_locate_rs:{start_lsn:{lsn:18446744073709551615}, loc_err:0}}) BACKTRACE:0x1860ef10 0x9c403b5 0x9bf96cd 0x9bf910f 0x9bf904c 0x9bf8e7d 0xc1f8e9f 0xc1f73fb 0xc18233a 0xc181723 0xc180b78 0xc25e86f 0x7f00f63b3ea5 0x7f00f59c0b0d
[2024-07-17 20:27:54.108771] INFO [TLOG] get_server_array_for_locate_start_lsn (ob_log_route_service.cpp:600) [31701][][T0][Y7B5AAC1692C9-0000000000000001-0-0] [lt=32] LSSvrList get_server_array_for_locate_start_lsn succ(ret=0, ret=“OB_SUCCESS”, router_key={cluster_id:1714618927, tenant_id:1006, ls_id:{id:1}})
[2024-07-17 20:27:54.108804] INFO [TLOG.FETCHER] locate_lsn_ (ob_log_ls_fetch_ctx.cpp:908) [31701][][T0][Y7B5AAC1692C9-0000000000000001-0-0] [lt=19] start lsn locate request launched(tls_id={tenant_id:1006, ls_id:{id:1}}, is_start_tstamp=true, start_tstamp="[2024-07-17 12:32:27.782967]", svr_cnt=3, svr_list=[{svr:“172.26.49.127:2882”, rpc_executed:false, rpc_err:0, svr_err:0, ls_err:0, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y0-0000000000000000-0-0}, {svr:“172.22.146.197:2882”, rpc_executed:false, rpc_err:0, svr_err:0, ls_err:0, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y0-0000000000000000-0-0}, {svr:“172.30.224.165:2882”, rpc_executed:false, rpc_err:0, svr_err:0, ls_err:0, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y0-0000000000000000-0-0}])
[2024-07-17 20:27:54.208892] ERROR issue_dba_error (ob_log.cpp:1875) [31701][][T0][Y7B5AAC1692C9-0000000000000001-0-0] [lt=27][errcode=-4388] Unexpected internal error happen, please checkout the internal errcode(errcode=-4016, file=“ob_log_start_lsn_locator.cpp”, line_no=928, info=“request start lsn from all server fail”)
[2024-07-17 20:27:54.208932] EDIAG [TLOG.FETCHER] get_result (ob_log_start_lsn_locator.cpp:928) [31701][][T0][Y7B5AAC1692C9-0000000000000001-0-0] [lt=39][errcode=-4016] request start lsn from all server fail(tls_id={tenant_id:1006, ls_id:{id:1}}, start_tstamp_ns=1721190747782967000, svr_cnt=3, svr_list_consumed=3, result_svr_list_idx=-1, svr_list=[{svr:“172.26.49.127:2882”, rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y7B5AAC1692C9-00000000005000CD-0-0}, {svr:“172.22.146.197:2882”, rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y7B5AAC1692C9-00000000006000CD-0-0}, {svr:“172.30.224.165:2882”, rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y7B5AAC1692C9-00000000007000CD-0-0}]) BACKTRACE:0x1860ef10 0x9c403b5 0x9d5df6d 0x9d5d99f 0x9d5d8e8 0x9bbaae7 0xc3ce420 0xc1f73e6 0xc18233a 0xc181723 0xc180b78 0xc25e86f 0x7f00f63b3ea5 0x7f00f59c0b0d
[2024-07-17 20:27:54.208965] ERROR issue_dba_error (ob_log.cpp:1875) [31701][][T0][Y7B5AAC1692C9-0000000000000001-0-0] [lt=32][errcode=-4388] Unexpected internal error happen, please checkout the internal errcode(errcode=0, file=“ob_log_ls_fetch_ctx.cpp”, line_no=933, info=“start lsn locate fail”)

#13

用的 oblogproxy 是哪个版本的？

#14

用的2.0.2
oblogproxy-2.0.2-100000012024060321.el7.x86_64.rpm

#15

在libobcdc.log里grep下关键字“get_data_dict_in_log_info succ|init obcdc succ”看下

#16

image
image967×282 8.36 KB

没有打印过这个关键字

#17

什么都没干，重新创建了一下binlog服务
CREATE BINLOG IF NOT EXISTS FOR TENANT oa.mx WITH CLUSTER URL http://xxxx:xxxx/services?Action=ObRootServiceInfo&User_ID=alibaba&UID=ocpmaster&ObRegion=oa;

image
image1006×270 6.37 KB

然后就不报错了。binlog日志也正常追加了
之前重新创建了n次。都异常。显示request start lsn from all server fail

#18

之前出问题有可能是数据字典被回收了，可以考虑调低数据字典生成周期：
ⅰ. 登录到对应租户下，执行alter system set dump_data_dictionary_to_log_interval = ‘1h’; （注意这里的提供的例子是1小时（1h），具体调整为多久需要根据具体情况来定）；
ⅱ. 或者登录到系统租户下，执行alter system set dump_data_dictionary_to_log_interval = ‘1h’ tenant all_user; 这个变更会对当前能看到的所有状态为NORMAL的用户租户生效；

1 个赞