be节点写入数据后宕机，并且无法重启（3.1版本）

💬 StarRocks 用户问答 日常运维
#1

be.INFO (26.3 MB) be.out (9.0 KB)

#2 
start time: Wed Mar 20 05:51:58 PM CST 2024
3.1.9 RELEASE (build e1c6e4e)
query_id:00000000-0000-0000-0000-000000000000, fragment_instance:00000000-0000-0000-0000-000000000000
tracker:process consumption: 103705368
tracker:query_pool consumption: 0
tracker:load consumption: 0
tracker:metadata consumption: 1655579
tracker:tablet_metadata consumption: 616261
tracker:rowset_metadata consumption: 1024170
tracker:segment_metadata consumption: 3164
tracker:column_metadata consumption: 11984
tracker:tablet_schema consumption: 78725
tracker:segment_zonemap consumption: 2488
tracker:short_key_index consumption: 0
tracker:column_zonemap_index consumption: 3584
tracker:ordinal_index consumption: 3840
tracker:bitmap_index consumption: 0
tracker:bloom_filter_index consumption: 0
tracker:compaction consumption: 0
tracker:schema_change consumption: 0
tracker:column_pool consumption: 0
tracker:page_cache consumption: 0
tracker:update consumption: 10
tracker:chunk_allocator consumption: 0
tracker:clone consumption: 0
tracker:consistency consumption: 0
tracker:datacache consumption: 0
tracker:replication consumption: 0
*** Aborted at 1710928318 (unix time) try "date -d @1710928318" if you are using GNU date ***
PC: @          0x58f1556 _ZZN9starrocksL17prepare_ops_datasERKNS_6SchemaERKSt6vectorIjSaIjEERKNS_5ChunkEPS3_IPFvPKviPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEESaISL_EEPS3_ISC_SaISC_EEENUlSC_iSJ_E6_4_FUNESC_iSJ_
*** SIGSEGV (@0x8) received by PID 36293 (TID 0x701034335640) from PID 8; stack trace: ***
    @          0x7cd4b2a google::(anonymous namespace)::FailureSignalHandler()
    @     0x70112d442520 (unknown)
    @          0x58f1556 _ZZN9starrocksL17prepare_ops_datasERKNS_6SchemaERKSt6vectorIjSaIjEERKNS_5ChunkEPS3_IPFvPKviPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEESaISL_EEPS3_ISC_SaISC_EEENUlSC_iSJ_E6_4_FUNESC_iSJ_
    @          0x58f365d starrocks::PrimaryKeyEncoder::encode_sort_key()
    @          0x5acf518 starrocks::MergeEntry<>::next()
    @          0x5ad2999 starrocks::RowsetMergerImpl<>::_do_merge_horizontally()
    @          0x5ad44fc starrocks::RowsetMergerImpl<>::_do_merge_vertically()
    @          0x5ad651c starrocks::RowsetMergerImpl<>::do_merge()
    @          0x5ac894f starrocks::compaction_merge_rowsets()
    @          0x3ebfcfc starrocks::TabletUpdates::_do_compaction()
    @          0x3ec13a6 starrocks::TabletUpdates::compaction()
    @          0x3c95451 starrocks::StorageEngine::_perform_update_compaction()
    @          0x3cb4607 starrocks::StorageEngine::_update_compaction_thread_callback()
    @          0xa34af34 execute_native_thread_routine
    @     0x70112d494ac3 (unknown)
    @     0x70112d526850 (unknown)
    @                0x0 (unknown)

v3.1.9 be compaction crash.

@trueeyu

#3

已联系上，正在查

#4

core_update_compact_44413.rar (12.4 MB)

#5

这个core文件是3.1.9下生成的吗？方便把生成core文件的二进制也发下吗？我用官网的3.1.9正式版本打开这个core文件堆栈不全。

#6

是3.1.9,文件已发

#7

CREATE TABLE imp_realtime_alarm_info (
id varchar(36) NOT NULL COMMENT “主键”,
xxx varchar(50) NULL COMMENT “创建人”,
xxx datetime NULL COMMENT “创建日期”,
xxx varchar(50) NULL COMMENT “更新人”
…
) ENGINE=OLAP
PRIMARY KEY( id )
COMMENT “实时报警信息表”
DISTRIBUTED BY HASH( id )
ORDER BY( id , park_id , equipment_id , equipment_id )
PROPERTIES (
“replication_num” = “3”,
“in_memory” = “false”,
“enable_persistent_index” = “true”,
“replicated_storage” = “true”,
“compression” = “LZ4”
);

建表时指定sort key时指定了两列相同的列equipment_id 导致触发了bug，暂时可以在建表指定sort key时注意不要指定相同的列来规避这个问题。后续会fix这个问题。

1赞

京ICP备2022026421号-1