<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hi Talur,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">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?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Regards,</div><div class="gmail_default" style="font-family:verdana,sans-serif">Gaurav</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 28, 2017 at 5:39 PM, Raghavendra Talur <span dir="ltr"><<a href="mailto:rtalur@redhat.com" target="_blank">rtalur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Sep 27, 2017 at 11:15 PM, Gaurav Chhabra<br>
<<a href="mailto:varuag.chhabra@gmail.com">varuag.chhabra@gmail.com</a>> wrote:<br>
> Hello Everyone,<br>
><br>
><br>
> I want to install Heketi server and client on Kubernetes. To ensure HA, i<br>
> would like to have replica set to 2 for it. However, i am not sure about the<br>
> Heketi db. Does it contain only static data about volumes, nodes etc (and<br>
> changes only when we perform some explicit operations such as add volumes<br>
> etc) OR will it create issues (concurrent write) if i have two replicas<br>
> running?<br>
><br>
<br>
</span>Yes, heketi updates the db only when a operation is performed. But<br>
replica set 2 won't work because bolt db opens the db file with read<br>
write lock and the second instance will fail to get one. You will end<br>
up with 2nd instance in read only mode.<br>
<br>
If I get it right, you are saying you can't afford to have heketi pod<br>
down even for the time duration when kubernetes respins the pod when<br>
it detects it is down?<br>
<br>
><br>
> Thanks,<br>
> Gaurav<br>
><br>
> ______________________________<wbr>_________________<br>
> heketi-devel mailing list<br>
> <a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
><br>
</blockquote></div><br></div>