Hi, There is no way to isolate the healing peer. Healing happens from the good brick to the bad brick. I guess your replica bricks are on a different peers. If you try to isolate the healing peer, it will stop the healing process itself.
What is the error you are getting while writing? It would be helpful to debug the issue, if you can provide us the output of the following commands: gluster volume info <vol_name> gluster volume heal <vol_name> info And also provide the client & heal logs. Thanks & Regards, Karthik On Mon, Oct 9, 2017 at 3:02 PM, ML <li...@websiteburo.com> wrote: > Hi everyone, > > I've been using gluster for a few month now, on a simple 2 peers > replicated infrastructure, 22Tb each. > > One of the peers has been offline last week during 10 hours (raid resync > after a disk crash), and while my gluster server was healing bricks, I > could see some write errors on my gluster clients. > > I couldn't find a way to isolate my healing peer, in the documentation or > anywhere else. > > Is there a way to avoid that ? Detach the peer while healing ? Some > tunning on the client side maybe ? > > I'm using gluster 3.9 on debian 8. > > Thank you for your help. > > Quentin > > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users