Displaying 20 results from an estimated 1000 matches similar to: "Proper command for replace-brick on distribute–replicate?"
2019 Jun 12
1
Proper command for replace-brick on distribute–replicate?
On 12/06/19 1:38 PM, Alan Orth wrote:
> Dear Ravi,
>
> Thanks for the confirmation?I replaced a brick in a volume last night
> and by the morning I see that Gluster has replicated data there,
> though I don't have any indication of its progress. The `gluster v
> heal volume info` and `gluster v heal volume info split-brain` are all
> looking good so I guess that's
2018 Jan 23
6
parallel-readdir is not recognized in GlusterFS 3.12.4
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 following in the client mount log:
[2018-01-23 10:24:24.048055] W [MSGID: 101174]
2018 Jan 30
1
parallel-readdir is not recognized in GlusterFS 3.12.4
----- Original Message -----
> From: "Alan Orth" <alan.orth at gmail.com>
> To: "Raghavendra Gowdappa" <rgowdapp at redhat.com>
> Cc: "gluster-users" <gluster-users at gluster.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,
2018 Jan 29
2
parallel-readdir is not recognized in GlusterFS 3.12.4
----- Original Message -----
> From: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> To: "Alan Orth" <alan.orth at gmail.com>
> Cc: "gluster-users" <gluster-users at gluster.org>
> Sent: Saturday, January 27, 2018 7:31:30 AM
> Subject: Re: [Gluster-users] parallel-readdir is not recognized in GlusterFS 3.12.4
>
> Adding
2018 Jan 27
0
parallel-readdir is not recognized in GlusterFS 3.12.4
Adding devs who work on it
On 23 Jan 2018 10:40 pm, "Alan Orth" <alan.orth at gmail.com> 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 Gluster Storage Server
> documentation[2]. I've successfully
2018 Jan 30
0
parallel-readdir is not recognized in GlusterFS 3.12.4
Thank you, Raghavendra. I guess this cosmetic fix will be in 3.12.6?
I'm also looking forward to seeing stability fixes to parallel-readdir and
or readdir-ahead in 3.12.x. :)
Cheers,
On Mon, Jan 29, 2018 at 9:26 AM Raghavendra Gowdappa <rgowdapp at redhat.com>
wrote:
>
>
> ----- Original Message -----
> > From: "Pranith Kumar Karampuri" <pkarampu at
2023 May 04
1
Simple quota in GlusterFS 11
Dear list,
I noticed that GlusterFS 11 introduces a new "simple quota" system.
According to the pull request? the implementation is based on Amar's
earlier proposal? and is inspired by work they did in Kadalu. Other than
that I don't see any documentation or discussion about these features.
Specifically, it seems that the implementation relies on the quota features
of the
2018 Jan 25
2
parallel-readdir is not recognized in GlusterFS 3.12.4
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 in the 3.10.0 and 3.11.0 release notes. In the
days after enabling these two options all of my
2018 Jan 26
1
parallel-readdir is not recognized in GlusterFS 3.12.4
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 same day as
the parallel-readdir and readdir-ahead options:
$ gluster volume set homes
2018 Jan 26
0
parallel-readdir is not recognized in GlusterFS 3.12.4
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 Orth <alan.orth at gmail.com> wrote:
> By the way, on a slightly related note, I'm pretty
2018 Jan 24
0
parallel-readdir is not recognized in GlusterFS 3.12.4
Adding Poornima to take a look at it and comment.
On Tue, Jan 23, 2018 at 10:39 PM, Alan Orth <alan.orth at gmail.com> 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 Gluster Storage Server
> documentation[2].
2018 Jan 23
2
BUG: After stop and start wrong port is advertised
Hello,
?
?
Will we also suffer from this regression in any of the (previously) fixed 3.10 releases? We kept 3.10 and hope to stay stable :/
Regards
Jo
?
?
-----Original message-----
From:Atin Mukherjee <amukherj at redhat.com>
Sent:Tue 23-01-2018 05:15
Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised
To:Alan Orth <alan.orth at gmail.com>;
CC:Jo
2018 Jan 23
0
BUG: After stop and start wrong port is advertised
3.10 doesn't have this regression, so you're safe.
On Tue, Jan 23, 2018 at 1:28 PM, Jo Goossens <jo.goossens at hosted-power.com>
wrote:
> Hello,
>
>
>
>
>
> Will we also suffer from this regression in any of the (previously) fixed
> 3.10 releases? We kept 3.10 and hope to stay stable :/
>
>
>
> Regards
>
> Jo
>
>
>
>
>
>
2018 Jan 22
2
BUG: After stop and start wrong port is advertised
Ouch! Yes, I see two port-related fixes in the GlusterFS 3.12.3 release
notes[0][1][2]. I've attached a tarball of all yesterday's logs from
/var/log/glusterd on one the affected nodes (called "wingu3"). I hope
that's what you need.
[0]
https://github.com/gluster/glusterfs/blob/release-3.12/doc/release-notes/3.12.3.md
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1507747
2018 Jan 23
0
BUG: After stop and start wrong port is advertised
So from the logs what it looks to be a regression caused by commit 635c1c3
( and the good news is that this is now fixed in release-3.12 branch and
should be part of 3.12.5.
Commit which fixes this issue:
COMMIT: https://review.gluster.org/19146 committed in release-3.12 by
\"Atin Mukherjee\" <amukherj at redhat.com> with a commit message-
glusterd: connect to an existing brick
2018 Jan 21
2
BUG: After stop and start wrong port is advertised
For what it's worth, I just updated some CentOS 7 servers from GlusterFS
3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had
to use Mike Hulsman's script to check the daemon port against the port in
the volume's brick info, update the port, and restart glusterd on each
node. Luckily I only have four servers! Hoping I don't have to do this
every time I
2018 Jan 22
0
BUG: After stop and start wrong port is advertised
The patch was definitely there in 3.12.3. Do you have the glusterd and
brick logs handy with you when this happened?
On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote:
> For what it's worth, I just updated some CentOS 7 servers from GlusterFS
> 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had
> to use Mike Hulsman's
2021 Nov 29
1
Gluster 10 used ports
Hi all,
Over the years I have been using the same ports in my firewall
for gluster 49152-49251 ( I know a bit too many ports but
local network with limited access)
Today I upgraded from version 9 to version 10 and it finally
went well until I ran:
gluster volume heal my-vol info summary
I got the answer:
Status: Transport endpoint is not connected
I realized that glusterfsd was using 50000+
2013 Oct 02
1
Shutting down a GlusterFS server.
Hi,
I have a 2-node replica volume running with GlusterFS 3.3.2 on Centos 6.4. I want to shut down one of the gluster servers for maintenance. Any best practice that is to be followed while turning off a server in terms of services etc. Or can I just shut down the server. ?
Thanks & Regards,
Bobby Jacob
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2017 Dec 02
1
BUG: After stop and start wrong port is advertised
On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com>
wrote:
> Hello Atin,
>
>
>
>
>
> Could you confirm this should have been fixed in 3.10.8? If so we'll test
> it for sure!
>
Fix should be part of 3.10.8 which is awaiting release announcement.
>
> Regards
>
> Jo
>
>
>
>
>
>
> -----Original