Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
5.5.0
-
None
Description
The rebalancing features for failover in 5.4 are great, but they don't address the basic scenario of a client seeking to connect to a network of brokers without requiring static configuration of particular connection addresses. For example a client (or broker) seeking to connect to a logical cluster of brokers needs to have concrete information for at least one broker. Once connected, the client will be able to use the information from the updateClusterClients exposed by the broker. But if that broker is down, the client cannot connect to the cluster in the first place. This puts the admin team back in the same position of having to manually configure and update all the clients. Although I have talked about clients above, I would really like to have this available for my brokers, so that I can logically segment my network into broker clusters, so having equivalent support in the networkConnector element is important.
I thought (incorrectly) that I might be able to configure the network connector using something like:
uri="failover:(multicast://default)"
or
uri="failover:(discovery:(multicast://default))"
If that could be supported I think it would be fairly intuitive.