Zookeeper is part of the Fabric architecture. I may be an option in the context of this
conversation, but its not something that we have already readily available.
In the most simplistic scenario, we have a remote Camel Http client that wants to connect
to cluster of wildfly servers that expose undertow endpoints. The Camel client wants to
use a load balancer <
http://camel.apache.org/load-balancer.html> like this
<camelContext id="camel"
xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="direct:start"/>
<loadBalance>
<roundRobin/>
<to uri="mock:x"/>
<to uri="mock:y"/>
<to uri="mock:z"/>
</loadBalance>
</route>
</camelContext>
I now wonder if it is possible to implement a camel load balancer variant that is able to
discover the initial topology of wildfly http endpoints and later react on changes in that
topology. Does that make sense?
cheers
— thomas
On 27 Nov 2015, at 00:09, Stuart Douglas <sdouglas(a)redhat.com>
wrote:
I'm not really sure exactly what you mean here, do you want the Undertow load
balancer to be able to use the data from the zookeper registry? Or are you talking about
having the Undertow endpoints register themselves with zookeeper?
Stuart
----- Original Message -----
> From: "Thomas Diesler" <tdiesler(a)redhat.com>
> To: "Stuart Douglas" <sdouglas(a)redhat.com>
> Cc: wildfly-dev(a)lists.jboss.org
> Sent: Thursday, 26 November, 2015 1:03:16 AM
> Subject: Allow Camel LoadBalancer to connect to clustered WildFly HTTP endpoints
>
> Hi Stuart/Friends,
>
>
https://github.com/wildfly-extras/wildfly-camel/issues/878
> <
https://github.com/wildfly-extras/wildfly-camel/issues/878>
>
> In fabric a camel load balancer can contact a (zookeeper) registry using a
> logical name to react to changes in server topology or for initial
> discovery. I wonder how this can/should be done in the context of undertow
> http endpoints on wildfly.
>
> cheers
> — thomas
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev