ieQu1

It can't be the only message in the logs... Normally EMQX outputs quite a few messages when it joins the cluster. Can I see full logs (not just warnings)?

Hello, Thanks for collecting this information, it helped to narrow down the search space. 1) The following logs indicate that the second core node successfully joined the cluster: ``` v5.4.1([email protected])1>...

Thanks. It looks like the second replicant wasn't able to reach the second core node for some reason. I will run some local tests to see what can trigger this...

Thanks for the info.

Hello, It might be related to this PR https://github.com/emqx/emqx/pull/11032 @zhongwencool could you please take a look?

Hi, Yes, in fact I did try to disable instant delivery, but strangely enough I got the same result: ``` _build/Concuerror/bin/concuerror --instant_delivery false -x code -x code_server -x error_handler -pa...

Version 5.0.21 is quite old, and it was the first minor version to include replicant support. We've merged several replicant-related bugfixes and improvements after that. Is this issue also reproducible...

Hello, No progress, sorry. I must have missed this new issue report among other other github notifications.

Hello, Thanks, these are interesting finds. We'll implement stricter validation.

Hello @panhao410 , First of all, thanks for your work and for providing very detailed reproduction instructions. I did some digging, and there is a configuration parameter `mqtt.strict_mode` that enables...