[heketi-devel] Heketi HA using Kubernetes
varuag.chhabra at gmail.com
Thu Sep 28 14:28:49 UTC 2017
Since there will be many applications which will be using Gluster volumes,
i would really prefer if i could ensure maximum availability. From what i
understand, since Heketi is managing Gluster and while creating storage
class, we specify the Heketi REST URL, so if it goes down, i hope
application pods will be affected, isn't it? If replicas is not feasible,
what are the options i can explore?
On Thu, Sep 28, 2017 at 5:39 PM, Raghavendra Talur <rtalur at redhat.com>
> On Wed, Sep 27, 2017 at 11:15 PM, Gaurav Chhabra
> <varuag.chhabra at gmail.com> wrote:
> > Hello Everyone,
> > I want to install Heketi server and client on Kubernetes. To ensure HA, i
> > would like to have replica set to 2 for it. However, i am not sure about
> > Heketi db. Does it contain only static data about volumes, nodes etc (and
> > changes only when we perform some explicit operations such as add volumes
> > etc) OR will it create issues (concurrent write) if i have two replicas
> > running?
> Yes, heketi updates the db only when a operation is performed. But
> replica set 2 won't work because bolt db opens the db file with read
> write lock and the second instance will fail to get one. You will end
> up with 2nd instance in read only mode.
> If I get it right, you are saying you can't afford to have heketi pod
> down even for the time duration when kubernetes respins the pod when
> it detects it is down?
> > Thanks,
> > Gaurav
> > _______________________________________________
> > heketi-devel mailing list
> > heketi-devel at gluster.org
> > http://lists.gluster.org/mailman/listinfo/heketi-devel
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the heketi-devel