[Gluster-users] Duplicated brick processes after restart of glusterd

[David Spisla]

Thank you for the clarification
Regards
David Spisla

Outlook für Android<https://aka.ms/ghei36> herunterladen

________________________________

David Spisla
Software Engineer
david.spisla at iternity.com
+49 761 59034852
iTernity GmbH
Heinrich-von-Stephan-Str. 21
79100 Freiburg
Deutschland
Website
 
Newsletter
 
Support Portal
iTernity GmbH. Geschäftsführer: Ralf Steinemann. 
​Eingetragen beim Amtsgericht Freiburg: HRB-Nr. 701332. 
​USt.Id DE242664311. [v01.023] 
From: Atin Mukherjee <amukherj at redhat.com>
Sent: Friday, June 14, 2019 7:03:05 PM
To: David Spisla
Cc: gluster-users at gluster.org List
Subject: Re: [Gluster-users] Duplicated brick processes after restart of glusterd

Please see https://bugzilla.redhat.com/show_bug.cgi?id=1696147 which is fixed in 5.6 . Although a race, I believe you're hitting this. Although the title of the bug reflects it to be shd + brick multiplexing combo, but it's applicable for bricks too.

On Fri, Jun 14, 2019 at 2:07 PM David Spisla <spisla80 at gmail.com<mailto:spisla80 at gmail.com>> wrote:
Dear Gluster Community,

this morning I had an interesting observation. On my 2 Node Gluster v5.5 System with 3 Replica1 volumes (volume1, volume2, test) I had duplicated brick processes (See output of ps aux in attached file duplicate_bricks.txt) for each of the volumes. Additionally there is a fs-ss volume which I use instead of gluster_shared_storage but this volume was not effected.

After doing some research I found a hint in glusterd.log . It seems to be that after a restart glusterd couldn't found the pid files for the freshly created brick processes and create new brick processes. One can see in the brick logs that for all the volumes that two brick processes were created just one after another.

Result: Two brick processes for each of the volumes volume1, volume2 and test.
"gluster vo status" shows that the pid number was mapped to the wrong port number for hydmedia and impax

But beside of that the volume was working correctly. I resolve that issue with a workaround. Kill all brick processes and restart glusterd. After that everything is fine.

Is this a bug in glusterd? You can find all relevant informations attached below

Regards
David Spisla
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org<mailto:Gluster-users at gluster.org>
https://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image639775.png
Type: image/png
Size: 382 bytes
Desc: image639775.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image717143.png
Type: image/png
Size: 412 bytes
Desc: image717143.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image965886.png
Type: image/png
Size: 6545 bytes
Desc: image965886.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image986774.png
Type: image/png
Size: 8191 bytes
Desc: image986774.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image804683.png
Type: image/png
Size: 522 bytes
Desc: image804683.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image955587.png
Type: image/png
Size: 591 bytes
Desc: image955587.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image082390.png
Type: image/png
Size: 775 bytes
Desc: image082390.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image294497.png
Type: image/png
Size: 508 bytes
Desc: image294497.png
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190617/bf3202ab/attachment-0015.png>