Environment
- Version: seekdb (OceanBase seekdb )
- Revision: 1-f84169fbd80d020887d038cdb0892703e28833f3
- Build Branch: HEAD
- Build Time: Aug 10 2026 10:45:34
- Build Flags: RelWithDebInfo
- Is this an RD-provided temporary version?: No
- Process ID / Port: PID 3662154, Port 2832
- Work ID: xJMcKDVRoXpa89uA
Description
During a DDL test (ddltest_duomo_lite), the Vsag component failed to create an index due to a std::bad_alloc exception. Subsequently, the observer returned error code ob_error=-4013.
Steps to Reproduce / Scenario
This occurred while running a workload in the test environment. The specific actions leading to the failure are not detailed, but the error logs are provided below.
Log Information
Logs were extracted using the command: grep -a 'YB427F000001-000658A85F106995-0-0' seekdb.log*
Key error entries:
[DATABASE_LOG_ALARM][ALARM] rule=ediag file=/data/1/seekdb-gitlab/ddltest_duomo_lite/log/pipeline-189961-job-919131/seekdb.log.20260810104736464 line=1306 [2026-08-10 10:47:13.095055] EDIAG [STORAGE.TRANS] submit_log_with_lock_ (ob_id_service.cpp:56) [3662154][observer][YB427F000001-000658A85F106995-0-0] [lt=6][errcode=-4109] submit log fail(ret=-4109, service_type_=1, last_id=1000001, limited_id=1000001) BACKTRACE:0x625f295 0x62b8332 0x1b1a5c7 0x1b1a05b 0x1b19e15 0x1b00e59 0x4ecc297 0x4ece9b1 0x4f1faee 0x4f1a9db 0x4f2b443 0x36b495f 0x2a326f2 0x2a31b7c 0x363e6a8 0x363e473 0x1b3035c 0x1b21355 0x1b21ff0 0x1b23eac 0x1b23bad 0x634e5f4 0x1cea481 0x1ce5612 0x1fad2bf 0x25e3879 0x25e2ed3 0x25d4e52 0x1ae928c 0x62762b0 0x1aeac93 0x149f2f301a72 0x1ae802e
[DATABASE_LOG_ALARM][ALARM] rule=ediag file=/data/1/seekdb-gitlab/ddltest_duomo_lite/log/pipeline-189961-job-919131/seekdb.log.20260810104736464 line=1346 [2026-08-10 10:47:13.190585] EDIAG [STORAGE.TRANS] submit_log_with_lock_ (ob_id_service.cpp:56) [3662154][observer][YB427F000001-000658A85F106995-0-0] [lt=9][errcode=-4109] submit log fail(ret=-4109, service_type_=1, last_id=1000001, limited_id=1000001) BACKTRACE:0x625f295 0x62b8332 0x1b1a5c7 0x1b1a05b 0x1b19e15 0x1b00e59 0x4ecc297 0x4ece9b1 0x4f1faee 0x4f1a9db 0x4f2b443 0x36b495f 0x2a326f2 0x2a31b7c 0x363e6a8 0x363e473 0x1b3035c 0x1b21355 0x1b21ff0 0x1b23eac 0x1b23bad 0x634e5f4 0x1cea481 0x1ce5612 0x1fad2bf 0x25e3879 0x25e2ed3 0x25d4e52 0x1ae928c 0x62762b0 0x1aeac93 0x149f2f301a72 0x1ae802e
[DATABASE_LOG_ALARM][ALARM] rule=ediag file=/data/1/seekdb-gitlab/ddltest_duomo_lite/log/pipeline-189961-job-919131/seekdb.log.20260810104736464 line=5788 [2026-08-10 10:47:13.435546] EDIAG [STORAGE.TRANS] ~ObMvccWriteGuard (ob_mvcc_ctx.cpp:377) [3662154][observer][YB427F000001-000658A85F1069FB-0-0] [lt=11][errcode=-6268] failed to submit log if neccesary(ret=-6268, is_freeze=false, tx_ctx={this:0x149f17527420, ref:5, trans_id:{txid:12}, is_exiting:false, trans_expired_time:1786330063421463, trans_need_wait_wrap:{receive_gts_ts_:[mts=0], need_wait_interval_us:0}, stc:[mts=0], ctx_create_time:1786330033421466}) BACKTRACE:0x625f295 0x62b8332 0x1af25bf 0x1af2053 0x1af1e1f 0x1aea279 0x45d2117 0x4cbc2aa 0x4e871ff 0x44976b5 0x4496f82 0x44892e3 0x4488944 0x4a0e0d1 0x2e7fbe6 0x2e80e8e 0x2e80c75 0x2e7ffef 0x2e9945f 0x2e9fe0d 0x2e9fbc0 0x2e85c03 0x2e85a27 0x37328ff 0x3738732 0x31b5f36 0x2a3556b 0x2a352bd 0x363f3ca 0x363f098 0x363e485 0x1b3035c 0x1b21355 0x1b21ff0 0x1b25118 0x1b24e0e 0x634fa69 0x1ca525d 0x1ca4b4f 0x1ca6b54 0x1ce70b0 0x1ce56e9 0x1fad2bf 0x25e3879 0x25e2ed3 0x25d4e52 0x1ae928c 0x62762b0 0x1aeac93 0x149f2f301a72 0x1ae802e
Full grep output is available in the original report.
Additional Context
- Reproducibility: Not specified (必现/偶现/不确定/其他).
- Test Changes: Not specified.
- Environment Abnormalities/Prompts: Not specified.
- Site Preserved: Not specified.
- Connection Strings / Deployment Info: Not provided.
- Work Item Type: This appears to be an internal test issue.
Environment
Description
During a DDL test (ddltest_duomo_lite), the Vsag component failed to create an index due to a
std::bad_allocexception. Subsequently, the observer returned error codeob_error=-4013.Steps to Reproduce / Scenario
This occurred while running a workload in the test environment. The specific actions leading to the failure are not detailed, but the error logs are provided below.
Log Information
Logs were extracted using the command:
grep -a 'YB427F000001-000658A85F106995-0-0' seekdb.log*Key error entries:
Full grep output is available in the original report.
Additional Context