[Bugs] [Bug 1493967] New: glusterd ends up with multiple uuids for the same node

bugzilla at redhat.com bugzilla at redhat.com
Thu Sep 21 08:48:46 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1493967

            Bug ID: 1493967
           Summary: glusterd ends up with multiple uuids for the same node
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org



Description of problem:
In a multi node cluster, if one of the glusterd instance goes down and comes
back, then there might be a race situation where glusterd needs to retrieve its
uuid (glusterd_retrieve_uuid) and at the same time as part of receiving a
friend handshake from other peer, glusterd iterates over the volume information
recieved from remote node and checks for if a brick is local or not by calling
MY_UUID which in turn calls glusterd_retrieve_uuid. This could end up in a
situation where for the same node glusterd ends up generating two UUID files in
/var/lib/glusterd. Following is the log snippet which confirms the above:

[2017-09-01 03:09:24.458030] I [glusterd.c:146:glusterd_uuid_init]
0-management: retrieved UUID: fd46a495-7e33-468f-88f6-63c815fac640  // thread 1
retrieve uuid from glusterd.info
[2017-09-01 03:09:24.458034] E [glusterd-store.c:2109:glusterd_retrieve_uuid]
0-: No previous uuid is present
//thread 2 can not retrieve uuid, because in thread1 the file pointer has
already become eof.
[2017-09-01 03:09:24.458041] E [glusterd-store.c:2117:glusterd_retrieve_uuid]
0-: Returning -1
[2017-09-01 03:09:24.458076] I [glusterd.c:176:glusterd_uuid_generate_save]
0-management: generated UUID: 190bb292-a296-4125-96da-42b247511cc4
[2017-09-01 03:09:24.458129] E [store.c:367:gf_store_save_value] 0-: Able to
store key: UUID,value: 190bb292-a296-4125-96da-42b247511cc4


Version-Release number of selected component (if applicable):
mainline

How reproducible:
rarely

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list