数据库发生了crash，gbased(8.6.2.33-R11.103194) got signal 11 ;但内存监控还是未满的

为提高效率，提问时请提供以下信息，问题描述清晰可优先响应。

【GBase版本】:8a mpp架构

【问题描述】*:业务反馈gbase节点异常了。查看system.log日志发现一直在报错，然后随即crash掉了。

240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Fatal signal 6 while backtracing
Fatal signal 6 while backtracing
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
terminate called recursively
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Fatal signal 6 while backtracing
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
terminate called recursively
Fatal signal 6 while backtracing
terminate called recursively
terminate called recursively
Fatal signal 6 while backtracing
Fatal signal 6 while backtracing
terminate called recursively
Fatal signal 6 while backtracing
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskCheckAsyncStatus
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskCheckAsyncStatus
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
terminate called recursively
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
Fatal signal 6 while backtracing
terminate called recursively
Fatal signal 6 while backtracing
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
terminate called recursively
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Fatal signal 6 while backtracing
Executor: exception: Invalid argument, task: RepTaskRecvData
240702  9:22:14 [ERROR] /opt/gnode/server/bin/gbased: Gbase general error: Invalid argument
Executor: exception: Invalid argument, task: RepTaskRecvData
terminate called recursively
Fatal signal 6 while backtracing
terminate called recursively
Fatal signal 6 while backtracing
Fatal signal 11 while backtracing
use SIG_DEF
01:22:14 UTC - gbased(8.6.2.33-R11.103194) got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=548
max_threads=512
threads_connected=277
It is possible that gbased could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1312842 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xc04dc2000
Attempting backtrace. You can use the following information to find out
where gbased died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f94ded84190 thread_stack 0x80000
/opt/gnode/server/bin/gbased(my_print_stacktrace+0x27)[0x1150cb7]
/opt/gnode/server/bin/gbased(handle_segfault+0x47d)[0x77642d]
/lib64/libpthread.so.0(+0xf5d0)[0x7fbc6552f5d0]
/opt/gnode/server/bin/gbased(_ZN8tcmalloc11ThreadCache21ReleaseToCentralCacheEPNS0_8FreeListEmi+0x10b)[0x12f0a8b]
/opt/gnode/server/bin/gbased(_ZN8tcmalloc11ThreadCache8ScavengeEv+0x40)[0x12f0da0]
/opt/gnode/server/bin/gbased(tc_delete+0x1da)[0x130fcda]
/opt/gnode/server/bin/gbased(_ZN12AttrLockInfoD1Ev+0x45)[0xe39e35]
/opt/gnode/server/bin/gbased(_ZN22TableAttrDpLockManagerD1Ev+0x51)[0xe35aa1]
/lib64/libc.so.6(+0x39b69)[0x7fbc62922b69]
/lib64/libc.so.6(+0x39bb7)[0x7fbc62922bb7]
/opt/gnode/server/bin/gbased(handle_segfault+0x360)[0x776310]
/lib64/libpthread.so.0(+0xf5d0)[0x7fbc6552f5d0]
/lib64/libstdc++.so.6(_ZNSs4_Rep9_S_createEmmRKSaIcE+0x59)[0x7fbc6328bc79]
/lib64/libstdc++.so.6(_ZNSs9_M_mutateEmmm+0x66)[0x7fbc6328be66]
/lib64/libstdc++.so.6(_ZNSs15_M_replace_safeEmmPKcm+0x1e)[0x7fbc6328c42e]
/opt/gnode/server/bin/gbased(_ZN11ExpressFile5CloseEv+0x2d)[0xf1118d]
/opt/gnode/server/bin/gbased(_ZN6PAAttr16GetValueLongBlobEyR13ExpressStringb+0x1f5)[0xc0f965]
/opt/gnode/server/bin/gbased(_ZN6PAAttr8GetValueEyR15ExpressDataTypeb+0x38c)[0xbfd56c]
/opt/gnode/server/bin/gbased(_ZN13TempTableImpl9GetRecordER4ListI4ItemER11MDFIteratorbRSt6vectorIP16LogicalAttributeSaIS8_EER14DataTypeRecord+0xd3)[0xc5b8b3]
/opt/gnode/server/bin/gbased(_ZN12ResultSender17SelectSend_SerialEx+0x905)[0xd829a5]
/opt/gnode/server/bin/gbased(_ZN12ResultSender6DoSendEx+0x623)[0xd834a3]
/opt/gnode/server/bin/gbased(_ZN12ResultSender4SendExb+0x13)[0xd79f33]
/opt/gnode/server/bin/gbased(_ZN9TempTable23FillMaterializedBuffersEyybbP12ResultSenderbPNS_4AttrE+0x28c)[0xfd109c]
/opt/gnode/server/bin/gbased(_ZN9TempTable11MaterializeEbP3THDP13select_resultP12ResultSender+0x16bf)[0xcfc9ff]
/opt/gnode/server/bin/gbased(_ZN13TempTableImpl11MaterializeEbP3THDP13select_resultP12ResultSender+0x51)[0xc5a2c1]
/opt/gnode/server/bin/gbased(_ZN13ExpressEngine7ExecuteEP3THDP6st_lexP13select_resultP18st_select_lex_unit+0xae9)[0xc71ce9]
/opt/gnode/server/bin/gbased(_ZN13ExpressEngine12HandleSelectEP3THDP6st_lexRP13select_resultmRiS7_S7_i+0xa23)[0xc73673]
/opt/gnode/server/bin/gbased(_Z20Express_HandleSelectP3THDP6st_lexRP13select_resultmRiS6_S6_i+0x81)[0xeca321]
/opt/gnode/server/bin/gbased(_Z21execute_sqlcom_selectP3THDP10TABLE_LIST+0xc5)[0x8d7865]
/opt/gnode/server/bin/gbased(_Z21gbase_execute_commandP3THD+0x21c9)[0x8e5dd9]
/opt/gnode/server/bin/gbased(_Z11gbase_parseP3THDPKcjPS2_+0x328)[0x8ee018]
/opt/gnode/server/bin/gbased(_Z16dispatch_command19enum_server_commandP3THDPcj+0x13ba)[0x8ef84a]
/opt/gnode/server/bin/gbased(_Z10do_commandP3THD+0xe2)[0x8f0662]
/opt/gnode/server/bin/gbased(libevent_thread_proc+0x1b9)[0x8d4439]
/lib64/libpthread.so.0(+0x7dd5)[0x7fbc65527dd5]
/lib64/libc.so.6(clone+0x6d)[0x7fbc629e6ead]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->thread_id=259989234
thd->killed=NOT_KILLED
thd->query at 7a9d1a410 =SELECT /*132.151.55.14_7754902_10_2024-07-02_09:22:08*/ /*+ TID('22346309470') */ concat(concat(`bd_app.stg_dwd_d_ema_electron_rail_detail`.`grid_code`, '|'), `bd_app.stg_dwd_d_ema_electron_rail_detail`.`sub_grid_code`) AS `area_code`, `bd_app.stg_dwd_d_ema_electron_rail_detail`.`grid_rail_json` AS `area_json`, `bd_app.stg_dwd_d_ema_electron_rail_detail`.`grid_hollow_rail_json` AS `hollow_area_json` FROM `bd_app`.`stg_dwd_d_ema_electron_rail_detail_n20` `bd_app.stg_dwd_d_ema_electrGbasedHeapUsed: HeapUsed(82319258448,5773245776,28685914448),SystemUsed(23010159844,0,0)

Dump finished, good luck.

240702 10:04:31 [Note] ==================================
240702 10:04:46 [Note] tcmalloc enabled
240702 10:04:46 [Note] aggressive_decommit enabled
240702 10:04:46 [Note] total_thread_cache use set value:1073741824
240702 10:06:12 [Note] Event Scheduler: Loaded 0 events
240702 10:06:12 [Note] Express is ready for connections.
socket: '/tmp/gbase_8a_5050.sock' port: 5050 103194

[如何处理]

请问该报错的原因是啥，如何处理，排查思路是如何的。