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
Hi Niklas,
Out of interest have you tried testing performance with
performance.stat-prefetch enabled?
--
Sam McLeod
@s_mcleod
https://smcleod.net
> On 14 Sep 2017, at 10:42 pm, Niklas Hambüchen wrote:
>
> Hi,
>
> I have a gluster 3.10 volume with a dir with ~1 million small
Hi,
I have a gluster 3.10 volume with a dir with ~1 million small files in
them, say mounted at /mnt/dir with FUSE, and I'm observing something weird:
When I list and stat them all using rsync, then the lstat() calls that
rsync does are incredibly fast (23 microseconds per call on average,
I have the %100 CPU usage issue when I restart a glusterd instance and
I do not have null client errors in log.
The issue was related to number of bricks/servers so I decreased the
brick count in volume. It resolved the problem.
On Thu, Sep 14, 2017 at 9:02 AM, Sam McLeod
The Gluster community is pleased to announce the release of Gluster
3.12.1 (packages available at [1,2,3]).
Release notes for the release can be found at [4].
We still carry a major issue that is reported in the release-notes as
follows,
- Expanding a gluster volume that is sharded may
Hi Serkan,
I was wondering if you resolved your issue with the high CPU usage and hang
after starting gluster?
I'm setting up a 3 server (replica 3, arbiter 1), 300 volume, Gluster 3.12
cluster on CentOS 7 and am having what looks to be exactly the same issue as
you.
With no volumes created