luster-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 appl
Hello Atin,
thank you for the clarification.
Am Fr., 14. Juni 2019 um 19:03 Uhr schrieb Atin Mukherjee <
amukh...@redhat.com>:
> 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
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
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
