I have switched from dragonfly 1.2.3 to 1.4.0 inside our Kubernetes cluster and now the pod don’t want to start with the following error:
I20230630 12:47:27.494930 1 init.cc:69] dragonfly running in opt mode.
I20230630 12:47:27.494998 1 dfly_main.cc:618] Starting dragonfly df-v1.4.0-6d4d740d6e2a060cbbbecd987ee438cc6e60de79
F20230630 12:47:27.495254 1 dfly_main.cc:493] Check failed: entry.size() == 3u (5 vs. 3)
*** Check failure stack trace: ***
@ 0x5640638a1ce3 google::LogMessage::SendToLog()
@ 0x56406389a4a7 google::LogMessage::Flush()
@ 0x56406389be2f google::LogMessageFatal::~LogMessageFatal()
@ 0x564063389c94 main
@ 0x7f479885d083 __libc_start_main
@ 0x56406338d08e _start
@ (nil) (unknown)
*** SIGABRT received at time=1688129247 on cpu 0 ***
PC: @ 0x7f479887c00b (unknown) raise
[failure_signal_handler.cc : 332] RAW: Signal 11 raised at PC=0x7f479885b941 while already in AbslFailureSignalHandler()
*** SIGSEGV received at time=1688129247 on cpu 0 ***
PC: @ 0x7f479885b941 (unknown) abort
Does anybody know a solution for that?