During a node power cycle, we sometimes can see this assert failure.
This maybe happen in the context of node restart and a lot of expose unexpose was there before restart and with a node powercyle, some how it caused this assert.
We can try to reproduce this issue by intensively update the meta blk and do randome kill of the process to reproduce.
[04/07/25 08:42:52.782] [access_mgr] [critical] [20] [meta_blks_mgr.cpp:1133] ******************** Assertion failure: =====> Expected '566382478' to be == to '2423040751' [type=RAFT_STATE_8a348a9a-9007-b00f-0190-c900ae920d4a], CRC mismatch: 566382478/2423040751, on mblk bid: BlkNum=14111804 nblks=1 chunk=2, context_sz: 22164
During a node power cycle, we sometimes can see this assert failure.
This maybe happen in the context of node restart and a lot of expose unexpose was there before restart and with a node powercyle, some how it caused this assert.
We can try to reproduce this issue by intensively update the meta blk and do randome kill of the process to reproduce.
[04/07/25 08:42:52.782] [access_mgr] [critical] [20] [meta_blks_mgr.cpp:1133] ******************** Assertion failure: =====> Expected '566382478' to be == to '2423040751' [type=RAFT_STATE_8a348a9a-9007-b00f-0190-c900ae920d4a], CRC mismatch: 566382478/2423040751, on mblk bid: BlkNum=14111804 nblks=1 chunk=2, context_sz: 22164