Re: Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Niels Hendriks <niels@xxxxxxxxxx>
Subject: Re: Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes
From: Sam McLeod <smj@xxxxxxxxxxxx>
Date: Wed, 15 Nov 2017 09:01:37 +1100
Cc: gluster-users@xxxxxxxxxxx
In-reply-to: <CAGGggOptfwriteHVa++=ZCJJV1M=fO35auuP9KOD8Azcqza1MQ@mail.gmail.com>
References: <CAGGggOptfwriteHVa++=ZCJJV1M=fO35auuP9KOD8Azcqza1MQ@mail.gmail.com>

By chance... it's not 3 replica, 1 arbiter is it?

--
Sam McLeod
https://smcleod.net
https://twitter.com/s_mcleod

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users

References:
- Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes
  - From: Niels Hendriks

Prev by Date: Re: Is there any performance impact in setting up every gluster client as a NFS server?
Next by Date: Re: Help with reconnecting a faulty brick
Previous by thread: Re: Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes
Next by thread: Re: Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes
Index(es):
- Date
- Thread

[Index of Archives] [Gluster Development] [Linux Filesytems Development] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux