Thank you for the acknowledgement.
On Mon, Sep 4, 2017 at 6:39 PM, lejeczek wrote:
> yes, I see things got lost in transit, I said before:
>
> I did from first time and now not rejected.
> now I'm restarting fourth(newly added) peer's glusterd
> and.. it seems to work. <- HERE! (even th
Executing "gluster volume set all cluster.op-version "on all
the existing nodes will solve this problem.
If issue still persists please provide me following logs (working-cluster
+ newly added peer)
1. glusterd.info file from /var/lib/glusterd from all nodes
2. glusterd.logs from all nodes
3. inf
I've also noticed - In case it's abnormal and might help -
that when rejected peer get probed it is present only on the
probing peer(though as rejected).
Remaining two peers do not show rejected peer in the status,
and rejected peer shows only the peer it got probed from.
On 01/09/17 07:30, Ga
hi, still tricky
whether I do or do not remove "tier-enabled=0" on rejected
peer, and try to restart glusterd service there, restart fails:
lusterd version 3.10.5 (args: /usr/sbin/glusterd -p
/var/run/glusterd.pid --log-level INFO)
[2017-09-01 07:41:08.251314] I [MSGID: 106478]
[glusterd.c:1
Logs from newly added node helped me in RCA of the issue.
Info file on node 10.5.6.17 consist of an additional property
"tier-enabled" which is not present in info file from other 3 nodes, hence
when gluster peer probe call is made, in order to maintain consistency
across the cluster cksum is comp
On 30/08/17 07:18, Gaurav Yadav wrote:
Could you please send me "info" file which is placed in
"/var/lib/glusterd/vols/" directory from all the
nodes along with
glusterd.logs and command-history.
Thanks
Gaurav
On Tue, Aug 29, 2017 at 7:13 PM, lejeczek
mailto:pelj...@yahoo.co.uk>> wrote:
On 30/08/17 07:18, Gaurav Yadav wrote:
Could you please send me "info" file which is placed in
"/var/lib/glusterd/vols/" 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(rejec
Could you please send me "info" file which is placed in
"/var/lib/glusterd/vols/" directory from all the nodes along with
glusterd.logs and command-history.
Thanks
Gaurav
On Tue, Aug 29, 2017 at 7:13 PM, lejeczek wrote:
> hi fellas,
> same old same
> in log of the probing peer I see:
> ...
> 20
hi fellas,
same old same
in log of the probing peer I see:
...
2017-08-29 13:36:16.882196] I [MSGID: 106493]
[glusterd-handler.c:3020:__glusterd_handle_probe_query]
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]
[
