单机部署一段时间后无法进行建表和插入操作

【 使用环境 】测试环境
【 OB or 其他组件 】OB
【 使用版本 】最新社区版 4.1.0.1
【问题描述】使用最小部署,单机版本地部署后,一切运行正常。但是运行一段时间后,无法进行建表、插入或更新数据,但查询没有问题。重启后又会恢复。
【复现路径】执行建表、插入数据都会超时。设置提示的超时时间为特别长后,也是一样的结果。自带租户及新建租户都有一样问题
【问题现象及影响】
因为重新部署后还暂未出现,先将部分日志贴出:
[2023-07-06 16:27:57.574148] INFO [STORAGE.TRANS] handle_timeout (ob_trans_part_ctx.cpp:575) [29261][T1002_TransTime][T1002][YB427F000001-0005FF54FE337438-0-0] [lt=79] handle timeout(ret=0, *this={this:0x7fc676a7c050, trans_id:{txid:1835657}, tenant_id:1002, is_exiting:false, trans_expired_time:1688632191773505, cluster_version:17179934721, trans_need_wait_wrap:{receive_gts_ts_:[mts=0], need_wait_interval_us:0}, stc:[mts=1688631191781838], ctx_create_time:1688631191780317}{ls_id:{id:1}, session_id:1, part_trans_action:3, pending_write:0, exec_info:{state:10, upstream:{id:-1}, participants:[{id:1}], incremental_participants:[], prev_record_lsn:{lsn:18446744073709551615}, redo_lsns:[], redo_log_no:0, multi_data_source:[], scheduler:“127.0.0.1:2882”, prepare_version:{val:18446744073709551615}, trans_type:0, next_log_entry_no:0, max_applied_log_ts:{val:18446744073709551615}, max_applying_log_ts:{val:18446744073709551615}, max_applying_part_log_no:9223372036854775807, max_submitted_seq_no:0, checksum:0, checksum_scn:{val:0}, max_durable_lsn:{lsn:18446744073709551615}, data_complete:false, is_dup_tx:false, prepare_log_info_arr:[], xid:{gtrid_str:"", bqual_str:"", format_id:1, gtrid_str_.ptr():“data_size:0, data:”, bqual_str_.ptr():“data_size:0, data:”, g_hv:0, b_hv:0}, need_checksum:true, is_sub2pc:false}, sub_state:{flag:4}, is_leaf():false, is_root():false, busy_cbs_.get_size():0, final_log_cb_:{ObTxBaseLogCb:{log_ts:{val:18446744073709551615}, lsn:{lsn:18446744073709551615}, submit_ts:0}, this:0x7fc676a7d7f8, is_inited_:true, trans_id:{txid:1835657}, ls_id:{id:1}, ctx:0x7fc676a7c050, tx_data_guard:{tx_data:NULL}, is_callbacked_:false, mds_range_:{count_:0}, cb_arg_array_:[], first_part_scn_:{val:18446744073709551615}}, ctx_tx_data_:{ctx_mgr_:0x7fc754404030, tx_data_guard_:{tx_data:{tx_id:{txid:1835657}, ref_cnt:1, state:“RUNNING”, commit_version:{val:18446744073709551615}, start_scn:{val:18446744073709551615}, end_scn:{val:18446744073709551615}, undo_status_list:{head:null, undo_node_cnt:0}}}, read_only_:false}, role_state_:0, start_replay_ts_:{val:18446744073709551615}, is_incomplete_replay_ctx_:false, mt_ctx_:{ObIMvccCtx={alloc_type=0 ctx_descriptor=1818326651 min_table_version=0 max_table_version=0 trans_version={val:4611686018427387903} commit_version={val:0} lock_wait_start_ts=0 replay_compact_version={val:0}} end_code=0 tx_status=0 is_readonly=false ref=0 trans_id={txid:1835657} ls_id=1 callback_alloc_count=2 callback_free_count=0 checksum=0 tmp_checksum=0 checksum_scn={val:0} redo_filled_count=0 redo_sync_succ_count=0 redo_sync_fail_count=0 main_list_length=3 unsynced_cnt=2 unsubmitted_cnt_=2 cb_statistics:[main=3, slave=0, merge=0, tx_end=0, rollback_to=0, fast_commit=0, remove_memtable=0]}, coord_prepare_info_arr_:[], upstream_state:10, retain_cause:-1, 2pc_role:-1, collected:[], ref:4, rec_log_ts:{val:18446744073709551615}, prev_rec_log_ts:{val:18446744073709551615}, lastest_snapshot:{val:18446744073709551615}, state_info_array:[], last_request_ts:1688631191781412}, tx_expired=false, commit_expired=false, delay=3000000)
【附件】

检查下clog是不是写满了,另外可以看下集群合并状态

出现异常,可以先保留日志,里边error和warn应该都能分析出来具体原因。或者ocp告警里找找严重价格告警