Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.4.0
-
None
-
None
Description
In network of brokers, duplicate route detection is done by checking broker ids. After the restart, the broker ids change, which can cause duplicate routes and messages stuck due to reached ttl.
We need to provide a mechanism for users to configure how their broker ids are assigned and make sure that they stay the same after the restart. Which will ensure correct duplicate route detection even after some of the broker in the mesh is restarted.