[Gluster-users] peer rejected but connected
peljasz at yahoo.co.uk
Wed Aug 30 10:32:44 UTC 2017
On 30/08/17 07:18, Gaurav Yadav wrote:
> Could you please send me "info" file which is placed in
> "/var/lib/glusterd/vols/<vol-name>" directory from all the
> nodes along with
> glusterd.logs and command-history.
I've send you some logs, thanks.
One more possibly interesting fact - now when
fourth(rejected) peer was detached I still see in
vol-name.client.10.5.6.17..... (which is IP of the rejected
and the same with .rpmsave
Only on two out of three peers which constitute a healthy
cluster. One peer does not have these files.
I wonder - was it upgrade from 3.8 to 3.10 that caused this
Can these file be deleted? And if yes would this be enough?
> On Tue, Aug 29, 2017 at 7:13 PM, lejeczek
> <peljasz at yahoo.co.uk <mailto:peljasz at yahoo.co.uk>> wrote:
> hi fellas,
> same old same
> in log of the probing peer I see:
> 2017-08-29 13:36:16.882196] I [MSGID: 106493]
> 0-glusterd: Responded to priv.xx.xx.priv.xx.xx.x,
> op_ret: 0, op_errno: 0, ret: 0
> [2017-08-29 13:36:16.904961] I [MSGID: 106490]
> 0-glusterd: Received probe from uuid:
> [2017-08-29 13:36:16.906477] E [MSGID: 106010]
> 0-management: Version of Cksums CO-DATA differ. local
> cksum = 4088157353, remote cksum = 2870780063 on peer
> [2017-08-29 13:36:16.907187] I [MSGID: 106493]
> 0-glusterd: Responded to 10.5.6.17 (0), ret: 0, op_ret: -1
> Why would adding a new peer make cluster jump to check
> checksums on a vol on that newly added peer? Is it why
> the peer gets rejected?
> That peer I'm hoping to add, was a member of the
> cluster in the past but I did "usual" wipe of
> /var/lib/gluster on candidate peer.
> a hint, solution would be great to hear.
> Gluster-users mailing list
> Gluster-users at gluster.org
> <mailto:Gluster-users at gluster.org>
More information about the Gluster-users