.org>
> > Sent: Tuesday, January 30, 2018 1:37:40 PM
> > Subject: Re: [Gluster-users] parallel-readdir is not recognized in
> GlusterFS 3.12.4
> >
> > Thank you, Raghavendra. I guess this cosmetic fix will be in 3.12.6?
>
> Yes.
>
> >
> > I'm also loo
:
>
>
>
>
> - Original Message -
> > From: "Pranith Kumar Karampuri" < pkara...@redhat.com >
> > To: "Alan Orth" < alan.o...@gmail.com >
> > Cc: "gluster-users" < gluster-users@gluster.org >
> > Sent: Saturd
riginal Message -
> > From: "Pranith Kumar Karampuri" <pkara...@redhat.com>
> > To: "Alan Orth" <alan.o...@gmail.com>
> > Cc: "gluster-users" <gluster-users@gluster.org>
> > Sent: Saturday, January 27, 2018 7:31:30 AM
>
- Original Message -
> From: "Pranith Kumar Karampuri" <pkara...@redhat.com>
> To: "Alan Orth" <alan.o...@gmail.com>
> Cc: "gluster-users" <gluster-users@gluster.org>
> Sent: Saturday, January 27, 2018 7:31:30 AM
>
@Vlad, yes I kept group metadata-cache and I also have
network.inode-lru-limit 9, but nothing else performance related.
@Pranith great, thank you.
Cheers,
On Sat, Jan 27, 2018 at 4:01 AM Pranith Kumar Karampuri
wrote:
> Adding devs who work on it
>
> On 23 Jan 2018
Adding devs who work on it
On 23 Jan 2018 10:40 pm, "Alan Orth" wrote:
> Hello,
>
> I saw that parallel-readdir was an experimental feature in GlusterFS
> version 3.10.0, became stable in version 3.11.0, and is now recommended for
> small file workloads in the Red Hat
Thanks for info Alan,
you've kept group metadata-cache, right?
I have them enabled as well
features.cache-invalidation=on
features.cache-invalidation-timeout=600
performance.stat-prefetch=on
performance.cache-invalidation=on
performance.md-cache-timeout=600
network.inode-lru-limit=5
but on
Dear Vlad,
I'm sorry, I don't want to test this again on my system just yet! It caused
too much instability for my users and I don't have enough resources for a
development environment. The only other variables that changed before the
crashes was the group metadata-cache[0], which I enabled the
can you please test parallel-readdir or readdir-ahead gives
disconnects? so we know which to disable
parallel-readdir doing magic ran on pdf from last year
https://events.static.linuxfound.org/sites/events/files/slides/Gluster_DirPerf_Vault2017_0.pdf
-v
On Thu, Jan 25, 2018 at 8:20 AM, Alan
Same here, even after update to 3.12.5-2
[2018-01-26 02:48:58.113996] W [MSGID: 101174]
[graph.c:363:_log_if_unknown_option] 0-q-readdir-ahead-0: option
'parallel-readdir' is not recognized
-v
On Tue, Jan 23, 2018 at 12:09 PM, Alan Orth wrote:
> Hello,
>
> I saw that
By the way, on a slightly related note, I'm pretty sure either
parallel-readdir or readdir-ahead has a regression in GlusterFS 3.12.x. We
are running CentOS 7 with kernel-3.10.0-693.11.6.el7.x86_6.
I updated my servers and clients to 3.12.4 and enabled these two options
after reading about them
Adding Poornima to take a look at it and comment.
On Tue, Jan 23, 2018 at 10:39 PM, Alan Orth wrote:
> Hello,
>
> I saw that parallel-readdir was an experimental feature in GlusterFS
> version 3.10.0, became stable in version 3.11.0, and is now recommended for
> small file
Hello,
I saw that parallel-readdir was an experimental feature in GlusterFS
version 3.10.0, became stable in version 3.11.0, and is now recommended for
small file workloads in the Red Hat Gluster Storage Server
documentation[2]. I've successfully enabled this on one of my volumes but I
notice the
13 matches
Mail list logo