Yes. After a reboot you could have a sync issue for up to a few hours. But this issue
persists now for 24 days. Additionally I see errors in the glustershd.log of the two hosts
that are having heal info for that volume. The first node shows as OK and has no errors in
its glustershd.log.
The errors are like this:
[2019-05-13 15:18:40.808945] W [MSGID: 114031]
[client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-engine-client-1: remote operation
failed. Path: <gfid:95ba9fb2-b0ae-436c-9c31-2779cf202235>
(95ba9fb2-b0ae-436c-9c31-2779cf202235) [No such file or directory]
[2019-05-13 15:18:40.809113] W [MSGID: 114031]
[client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-engine-client-2: remote operation
failed. Path: <gfid:95ba9fb2-b0ae-436c-9c31-2779cf202235>
(95ba9fb2-b0ae-436c-9c31-2779cf202235) [No such file or directory]
[root@node02 ~]#
Looks like the first node is sane and the other two are the masters but are not so sane.
:-/