Displaying 4 results from an estimated 4 matches for "my_volume_name".
2017 Sep 15
3
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...of times and is especially noisey when any node is running gluster volume set <volname> <option> <value>.
and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log:
[2017-09-15 00:36:21.654242] W [MSGID: 114010] [client-callback.c:28:client_cbk_fetchspec] 0-my_volume_name-client-0: this function should not be called
---
Cluster configuration:
Gluster 3.12
CentOS 7.4
Replica 3, Arbiter 1
NFS disabled (using Kubernetes with the FUSE client)
Each node is 8 Xeon E5-2660 with 16GB RAM virtualised on XenServer 7.2
root at int-gluster-03:~ # gluster get
glusterd st...
2017 Sep 18
2
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...en any node is running gluster volume set <volname> <option> <value>.
>>
>> and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log:
>>
>> [2017-09-15 00:36:21.654242] W [MSGID: 114010] [client-callback.c:28:client_cbk_fetchspec] 0-my_volume_name-client-0: this function should not be called
>>
>>
>> ---
>>
>>
>> Cluster configuration:
>>
>> Gluster 3.12
>> CentOS 7.4
>> Replica 3, Arbiter 1
>> NFS disabled (using Kubernetes with the FUSE client)
>> Each node is 8 X...
2017 Sep 18
0
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...oisey when any
> node is running gluster volume set <volname> <option> <value>.
>
> and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log:
>
> [2017-09-15 00:36:21.654242] W [MSGID: 114010]
> [client-callback.c:28:client_cbk_fetchspec] 0-my_volume_name-client-0:
> this function should not be called
>
>
> ---
>
>
> Cluster configuration:
>
> Gluster 3.12
> CentOS 7.4
> Replica 3, Arbiter 1
> NFS disabled (using Kubernetes with the FUSE client)
> Each node is 8 Xeon E5-2660 with 16GB RAM virtualised on XenServ...
2017 Sep 25
0
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...en any node is running gluster volume set <volname> <option> <value>.
>>
>> and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log:
>>
>> [2017-09-15 00:36:21.654242] W [MSGID: 114010] [client-callback.c:28:client_cbk_fetchspec] 0-my_volume_name-client-0: this function should not be called
>>
>>
>> ---
>>
>>
>> Cluster configuration:
>>
>> Gluster 3.12
>> CentOS 7.4
>> Replica 3, Arbiter 1
>> NFS disabled (using Kubernetes with the FUSE client)
>> Each node is 8 X...