On Fri, Sep 1, 2017 at 9:42 AM, Michael Scherer wrote:
> Le vendredi 01 septembre 2017 à 14:02 +0100, Michael Scherer a écrit :
>> Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
>> > Hello,
>> >
>> > To reduce confusion, we've setup docs.gluster.org pointing to
Hi,
I got these errors 3 times since I'm testing gluster with nfs-ganesha. The
clients are php apps and when this happen, clients got strange php session
error. Below, the first error only happen once but other errors happen every
time a clients try to create a new session file. To make php
Hi
We're seeing high? number of pending calls on two of our glusterfs 3.10
clusters.
We have not tried to tune anything except changing server.event-threads: 2
gluster volume status callpool | grep Pending results in various numbers
but more often that not a fair few of the bricks have 200-400
Le vendredi 01 septembre 2017 à 14:02 +0100, Michael Scherer a écrit :
> Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
> > Hello,
> >
> > To reduce confusion, we've setup docs.gluster.org pointing to
> > gluster.readthedocs.org. Both URLs will continue to work for the
> >
Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
> Hello,
>
> To reduce confusion, we've setup docs.gluster.org pointing to
> gluster.readthedocs.org. Both URLs will continue to work for the
> forseeable
> future.
>
> Please update any references that you control to point to
>
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,
My answers inline.
> Am 01.09.2017 um 04:19 schrieb Ben Turner :
>
> I re-added gluster-users to get some more eye on this.
>
> - Original Message -
>> From: "Christoph Schäbel"
>> To: "Ben Turner"
>> Sent:
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]
Hi,
You can find pstack sampes here:
https://www.dropbox.com/s/6gw8b6tng8puiox/pstack_with_debuginfo.zip?dl=0
Here is the first one:
Thread 8 (Thread 0x7f92879ae700 (LWP 78909)):
#0 0x003d99c0f00d in nanosleep () from /lib64/libpthread.so.0
#1 0x00310fe37d57 in gf_timer_proc () from
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
10 matches
Mail list logo