By the way, a possible new feature would be to implement a locking mechanism based on Cellar, leveraging jClouds, Hazelcast, Ignite, Zookeeper, whatever.
I already started something with jClouds. Regards JB On 19/06/2018 16:09, Jean-Baptiste Onofré wrote: > Hi, > > you can't do that with Cellar (again, Cellar is active/active). > > For "pure" failover, you have to use the lock mechanism. Your two docker > processes should: > > 1. use a shared filesystem (like NFS) to store the lock > 2. a database lock > > Kubernetes POD could be used with Cellar to discover the cluster nodes, > but not for failover. > > Regards > JB > > On 19/06/2018 16:06, imranrazakhan wrote: >> Ok, thanks for updates. >> >> Please provide details how we can achieve failover behavior(A 'hot' standby >> instance) like mentioned in >> >> >> https://svn.apache.org/repos/asf/karaf/site/production/manual/latest-3.0.x/failover.html >> >> >> in Docker environment? >> >> How karaf support to communicate between two images/pods. >> >> As we can use kubernetes for orchestration of instances but i am not clear >> how to achieve "A 'hot' standby instance" with it. Kubernetes will start and >> stop bundles regardless of statuses of bundles of karaf pods >> >> >> >> -- >> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html >> > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
