Open chandu-atina opened 8 years ago
chronos can't redirect the leader even the leader changed in my mind. you only manually pick the leader ip
You shouldn't need to do anything special in terms of HA. Start Chronos on the masters and Mesos will make one instance the leader check the mesos frameworks tab to verify this. If you're also using mesos-dns the active Chronos leader will always be accessible via http://chronos-2.4.0.mesos:4400/
I have three server A,B,C on each machine I'm running chronos, zookeeper, mesos-master, mesos-slave.
Chronos cantact mesos-master using zookeeper url hence it automatically picks leading master even if some node is down. I'm having high availability here.
Even Chronos run in cluster mode so accessing any of the Chronos I see same list of jobs and everything works fine.
Problem I have here is, Chronos is accessible with any of the three URLs
http://server_node_1:4400 http://server_node_2:4400 http://server_node_3:4400
Is there a way to configure Chronos Cluster with some kind of HAProxy?
My application should be talking to single URL, it has to take care of routing to active Chronos node even if some node is down.