<html><head></head><body><div class="ydp4b3a25f5yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Strahil,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I have the gluster setup on centos 7 cluster.I see glusterfsd service and it is in inactive state.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div><div>systemctl status glusterfsd.service</div><div>● glusterfsd.service - GlusterFS brick processes (stopping only)</div><div> Loaded: loaded (/usr/lib/systemd/system/glusterfsd.service; disabled; vendor preset: disabled)</div><div> Active: inactive (dead)</div><div><br></div></div><br></div><div dir="ltr" data-setdir="false">so you mean starting this service in all the nodes where gluster volumes are created, will solve the issue ?<br></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thanks,</div><div dir="ltr" data-setdir="false">Ahemad</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="yahoo_quoted_2474528784" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, 16 June, 2020, 10:12:22 pm IST, Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi ahemad,<br clear="none"><br clear="none">the script kills all gluster processes, so the clients won't wait for the timeout before switching to another node in the TSP.<br clear="none"><br clear="none">In CentOS/RHEL, there is a systemd service called 'glusterfsd.service' that is taking care on shutdown to kill all processes, so clients won't hung.<br clear="none"><br clear="none">systemctl cat glusterfsd.service --no-pager<br clear="none"># /usr/lib/systemd/system/glusterfsd.service<br clear="none">[Unit]<br clear="none">Description=GlusterFS brick processes (stopping only)<br clear="none">After=network.target glusterd.service<br clear="none"><br clear="none">[Service]<br clear="none">Type=oneshot<br clear="none"># glusterd starts the glusterfsd processed on-demand<br clear="none"># /bin/true will mark this service as started, RemainAfterExit keeps it active<br clear="none">ExecStart=/bin/true<br clear="none">RemainAfterExit=yes<br clear="none"># if there are no glusterfsd processes, a stop/reload should not give an error<br clear="none">ExecStop=/bin/sh -c "/bin/killall --wait glusterfsd || /bin/true"<br clear="none">ExecReload=/bin/sh -c "/bin/killall -HUP glusterfsd || /bin/true"<br clear="none"><br clear="none">[Install]<br clear="none">WantedBy=multi-user.target<br clear="none"><br clear="none">Best Regards,<br clear="none">Strahil Nikolov<br clear="none"><div class="yqt3576088527" id="yqtfd16109"><br clear="none">На 16 юни 2020 г. 18:41:59 GMT+03:00, ahemad shaik <<a shape="rect" ymailto="mailto:ahemad_shaik@yahoo.com" href="mailto:ahemad_shaik@yahoo.com">ahemad_shaik@yahoo.com</a>> написа:<br clear="none">> Hi, <br clear="none">>I see there is a script file in below mentioned path in all nodes using<br clear="none">>which gluster volume<br clear="none">>created./usr/share/glusterfs/scripts/stop-all-gluster-processes.sh<br clear="none">>I need to create a system service and when ever there is some server<br clear="none">>down, we need to call this script or we need to have it run always it<br clear="none">>will take care when some node is down to make sure that client will not<br clear="none">>have any issues in accessing mount point ?<br clear="none">>can you please share any documentation on how to use this.That will be<br clear="none">>great help.<br clear="none">>Thanks,Ahemad<br clear="none">><br clear="none">><br clear="none">><br clear="none">><br clear="none">>On Tuesday, 16 June, 2020, 08:59:31 pm IST, Strahil Nikolov<br clear="none">><<a shape="rect" ymailto="mailto:hunter86_bg@yahoo.com" href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>> wrote: <br clear="none">> <br clear="none">> Hi Ahemad,<br clear="none">><br clear="none">>You can simplify it by creating a systemd service that will call <br clear="none">>the script.<br clear="none">><br clear="none">>It was already mentioned in a previous thread (with example), so <br clear="none">>you can just use it.<br clear="none">><br clear="none">>Best Regards,<br clear="none">>Strahil Nikolov<br clear="none">><br clear="none">>На 16 юни 2020 г. 16:02:07 GMT+03:00, Hu Bert <<a shape="rect" ymailto="mailto:revirii@googlemail.com" href="mailto:revirii@googlemail.com">revirii@googlemail.com</a>><br clear="none">>написа:<br clear="none">>>Hi,<br clear="none">>><br clear="none">>>if you simply reboot or shutdown one of the gluster nodes, there might<br clear="none">>>be a (short or medium) unavailability of the volume on the nodes. To<br clear="none">>>avoid this there's script:<br clear="none">>><br clear="none">>>/usr/share/glusterfs/scripts/stop-all-gluster-processes.sh (path may<br clear="none">>>be different depending on distribution)<br clear="none">>><br clear="none">>>If i remember correctly: this notifies the clients that this node is<br clear="none">>>going to be unavailable (please correct me if the details are wrong).<br clear="none">>>If i do reboots of one gluster node, i always call this script and<br clear="none">>>never have seen unavailability issues on the clients.<br clear="none">>><br clear="none">>><br clear="none">>>Regards,<br clear="none">>>Hubert<br clear="none">>><br clear="none">>>Am Mo., 15. Juni 2020 um 19:36 Uhr schrieb ahemad shaik<br clear="none">>><<a shape="rect" ymailto="mailto:ahemad_shaik@yahoo.com" href="mailto:ahemad_shaik@yahoo.com">ahemad_shaik@yahoo.com</a>>:<br clear="none">>>><br clear="none">>>> Hi There,<br clear="none">>>><br clear="none">>>> I have created 3 replica gluster volume with 3 bricks from 3 nodes.<br clear="none">>>><br clear="none">>>> "gluster volume create glustervol replica 3 transport tcp<br clear="none">>node1:/data<br clear="none">>>node2:/data node3:/data force"<br clear="none">>>><br clear="none">>>> mounted on client node using below command.<br clear="none">>>><br clear="none">>>> "mount -t glusterfs node4:/glustervol /mnt/"<br clear="none">>>><br clear="none">>>> when any of the node (either node1,node2 or node3) goes down,<br clear="none">>gluster<br clear="none">>>mount/volume (/mnt) not accessible at client (node4).<br clear="none">>>><br clear="none">>>> purpose of replicated volume is high availability but not able to<br clear="none">>>achieve it.<br clear="none">>>><br clear="none">>>> Is it a bug or i am missing anything.<br clear="none">>>><br clear="none">>>><br clear="none">>>> Any suggestions will be great help!!!<br clear="none">>>><br clear="none">>>> kindly suggest.<br clear="none">>>><br clear="none">>>> Thanks,<br clear="none">>>> Ahemad<br clear="none">>>><br clear="none">>>> ________<br clear="none">>>><br clear="none">>>><br clear="none">>>><br clear="none">>>> Community Meeting Calendar:<br clear="none">>>><br clear="none">>>> Schedule -<br clear="none">>>> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br clear="none">>>> Bridge: <a shape="rect" href="https://bluejeans.com/441850968" target="_blank">https://bluejeans.com/441850968</a><br clear="none">>>><br clear="none">>>> Gluster-users mailing list<br clear="none">>>> <a shape="rect" ymailto="mailto:Gluster-users@gluster.org" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br clear="none">>>> <a shape="rect" href="https://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br clear="none">>>________<br clear="none">>><br clear="none">>><br clear="none">>><br clear="none">>>Community Meeting Calendar:<br clear="none">>><br clear="none">>>Schedule -<br clear="none">>>Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br clear="none">>>Bridge: <a shape="rect" href="https://bluejeans.com/441850968" target="_blank">https://bluejeans.com/441850968</a><br clear="none">>><br clear="none">>>Gluster-users mailing list<br clear="none">>><a shape="rect" ymailto="mailto:Gluster-users@gluster.org" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br clear="none">>><a shape="rect" href="https://lists.gluster.org/mailman/listinfo/gluster-users " target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users </a> </div></div></div>
</div>
</div></body></html>