observer4.3.1.0 CRASH ERROR

【 使用环境 】生产环境
【 OB or 其他组件 】observer
【 使用版本 】4.3.1.0
【问题描述】ocp报错 CRASH ERROR,并且在 observer.log 日志中确认存在,并且进程挂掉
【复现路径】无
【附件及日志】core dump如下

warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.

warning: File "/usr/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".

warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
Core was generated by `/home/admin/xxx_xxx/oceanbase/bin/observer'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000fffe52d73780 in raise () from /usr/lib64/libpthread.so.0
[Current thread is 1 (LWP 2954538)]
(gdb) bt
#0  0x0000fffe52d73780 in raise () from /usr/lib64/libpthread.so.0
#1  0x0000aaab53a9f784 in oceanbase::common::coredump_cb(int, int, void*, void*) ()
#2  <signal handler called>
#3  0x0000aaab4f462bb4 in oceanbase::storage::ObTabletDirectLoadMgr::calc_range(long) ()
#4  0x0000aaab4f46507c in oceanbase::storage::ObTabletDirectLoadMgr::close_sstable_slice(bool, oceanbase::storage::ObDirectLoadSliceInfo const&, oceanbase::share::SCN const&, long, oceanbase::storage::ObInsertMonitor*, oceanbase::blocksstable::ObMacroDataSeq&) ()
#5  0x0000aaab4f433cd0 in oceanbase::storage::ObTenantDirectLoadMgr::close_sstable_slice(oceanbase::storage::ObDirectLoadSliceInfo const&, oceanbase::storage::ObInsertMonitor*, oceanbase::blocksstable::ObMacroDataSeq&) ()
#6  0x0000aaab4caa5dbc in oceanbase::sql::ObPxMultiPartSSTableInsertOp::inner_get_next_row() ()
#7  0x0000aaab4c0a2a84 in oceanbase::sql::ObOperator::get_next_row() ()
#8  0x0000aaab4a82d9d0 in oceanbase::sql::ObOperator::get_next_batch_with_onlyone_row() ()
#9  0x0000aaab4befc26c in oceanbase::sql::ObOperator::get_next_batch(long, oceanbase::sql::ObBatchRows const*&) ()
#10 0x0000aaab490149f0 in oceanbase::sql::ObPxTransmitOp::next_batch(long) ()
#11 0x0000aaab4befbd94 in oceanbase::sql::ObOperator::get_next_batch(long, oceanbase::sql::ObBatchRows const*&) ()
#12 0x0000aaab49011bf0 in oceanbase::sql::ObPxTransmitOp::fetch_first_row() ()
#13 0x0000aaab48f89aec in oceanbase::sql::ObPxTransmitOp::inner_open() ()
#14 0x0000aaab48ff8918 in oceanbase::sql::ObPxReduceTransmitOp::inner_open() ()
#15 0x0000aaab4bf3937c in oceanbase::sql::ObOperator::open() ()
#16 0x0000aaab4b04fef4 in oceanbase::sql::ObPxTaskProcess::process() ()
#17 0x0000aaab4b08861c in oceanbase::sql::PxWorkerFunctor::operator()(bool) ()
#18 0x0000aaab4c385cdc in oceanbase::omt::ObPxPool::run1() ()
#19 0x0000aaab47c58ac0 in oceanbase::omt::ObPxPool::run(long) ()
#20 0x0000aaab540c9e28 in oceanbase::lib::Thread::__th_start(void*) ()
#21 0x0000fffe52d6878c in ?? () from /usr/lib64/libpthread.so.0
#22 0x0000fffe52cb508c in ?? () from /usr/lib64/libc.so.6

1.可以参考 OceanBase应急三板斧 恢复业务

https://open.oceanbase.com/blog/13250502949
2. 麻烦发下observer.log,core文件 以及使用obdiag分析下报错前后10分钟到日志,参考命令及文档如下

obdiag analyze log --from “2023-10-08 10:25:00” --to “2023-10-08 11:30:00”

https://www.oceanbase.com/docs/common-obdiag-cn-1000000001214443

3.OB server 运行了多久挂掉的?

您好,

上次的启动时间是8月9号,应该运行了20多天了

内存设置的比较高, core dump 有 80G,怎么发呢?

日志正在按照要求分析中

最新的一个core文件 压缩后多大呢?我们联系下你

已确认为已知问题,可升级到432最新BP。