As we've mentioned previously, replicated LevelDB is not a supported configuration and support is being removed in the next release, no one on this mailing list knows enough about it to help you troubleshoot problems, and if you do choose to use it despite those things you should be prepared to use the source code and a debugger to answer your own questions and implement your own fixes.
Tim On Tue, Jul 20, 2021, 7:22 PM ヤ艾枫o.-- <1169114...@qq.com.invalid> wrote: > Hello > I have set the policy of not discarding the dead letter queue, and set the > message will enter the dead letter queue after expiration. When I restart > the broker of three nodes, I sometimes find that the statistics of > activemq.dlq of each node are inconsistent, mainly the value of > QueueSize . And sometimes the value of QueueSize is negative. > > > The version number used is: activemq5.15.9 + zookeeper 3.4.5 > > > I found that the message synchronization strategy of this cluster mode is > semi synchronous by consulting the data. Is it because the message of > master node has not been synchronized to other slave nodes?If so, how to > set the time interval for synchronizing other nodes? At the same time, I'm > setting the number of expired messages to be less than 200
