EventBus address always get first one about consul-cluster-manager HOT 3 CLOSED

@leotu - let me clarify something, so you have 3 nodes where every node is registered as a consumer under "abc-addr", and the same every node fires a message (ONLY ONCE) toward "abc-addr" - processing of those messages ends up on the ONLY ONE node.

If this is the case -> given behavior seems to be correct. Normally round robin load balancing takes place on the "client node" (so the requester resolves the subscriber on the fly based on available list of subscribers.) If each of the requesters sends a message just once -> those messages will get processed by the node that gets resolved.

Now if you have a requester node sending multiple messages toward address "abc-addr" (and say you have multiple subscribers under "adc-addr") -> then normally you message should get balanced in dummy round robin fashion between subscribers.

I'll try to verify if load balancing is behaving as expected in this implementation as soon as I can and I'll get back to this.

from consul-cluster-manager.

@leotu , just FYI I've just released 1.2.2 (compatible with vert.x-core 3.8.2) which also included a bit enriched way of retrieving/resolving subscribers from consul (see #16 ). Can you please verify this issue with the new (1.2.2) version ? Looking forward seeing your results.

Thanks in advance!

from consul-cluster-manager.

Getting this one closed.

from consul-cluster-manager.