Re: [Gluster-users] 0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)

The 3.12.1 CentOS Storage SIG have now been released: http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/ Big thank you to Niels de Vos from Redhat! -- Sam McLeod @s_mcleod https://smcleod.net > On 25 Sep 2017, at 10:

Re: [Gluster-users] 0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)

FYI - I've been testing the Gluster 3.12.1 packages with the help of the SIG maintainer and I can confirm that the logs are no longer being filled with NFS or null client errors after the upgrade. -- Sam McLeod @s_mcleod https://smcleod.net > On 18 Sep 2017, at 10:14 pm, Sam McLeod wrote: >

Re: [Gluster-users] 0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)

Thanks Milind, Yes I’m hanging out for CentOS’s Storage / Gluster SIG to release the packages for 3.12.1, I can see the packages were built a week ago but they’re still not on the repo :( -- Sam > On 18 Sep 2017, at 9:57 pm, Milind Changire wrote: > > Sam, > You might want to give glusterfs-

Re: [Gluster-users] 0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)

Sam, You might want to give glusterfs-3.12.1 a try instead. On Fri, Sep 15, 2017 at 6:42 AM, Sam McLeod wrote: > Howdy, > > I'm setting up several gluster 3.12 clusters running on CentOS 7 and have > having issues with glusterd.log and glustershd.log both being filled with > errors relating to

Re: [Gluster-users] 0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)

- Original Message - > From: "Sam McLeod" > To: gluster-users@gluster.org > Sent: Friday, September 15, 2017 6:42:13 AM > Subject: [Gluster-users] 0-client_t: null client [Invalid argument] & high > CPU usage (Gluster 3.12) > > Howdy, > > I&#

[Gluster-users] 0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)

Howdy, I'm setting up several gluster 3.12 clusters running on CentOS 7 and have having issues with glusterd.log and glustershd.log both being filled with errors relating to null client errors and client-callback functions. They seem to be related to high CPU usage across the nodes although I d