Re: [Gluster-devel] Release 3.11: Pending features and reviews (2 days to branching)

On Wed, Apr 26, 2017 at 5:11 AM, Shyam wrote: > Hi, > > This mail should have been out 3-4 days earlier than now as branching is 2 > days away, but hopefully it is not too late. > > The current release scope can be seen at [1]. > > If you do *not* recognize your nick in the

Re: [Gluster-devel] Statedumps as non-root can not be saved (under /var/run/gluster/...)

On Tue, Apr 25, 2017 at 11:23 PM, Niels de Vos wrote: > Hi, > > Recently a new ability to trigger statedumps through the Gluster-CLI [0] > has been added. This makes it possible to get statedump from > applications that use gfapi. By default, statedumps are saved under >

Re: [Gluster-devel] Master regressions broken (by me!)

On 04/25/2017 09:03 PM, Shyam wrote: I merged https://review.gluster.org/#/c/16806/ which depends on https://review.gluster.org/#/c/16796/ and hence is failing regressions for all other patches. Fixing it up as I type this mail! Merged the dependent patch [1] (it had the required review

[Gluster-devel] Master regressions broken (by me!)

I merged https://review.gluster.org/#/c/16806/ which depends on https://review.gluster.org/#/c/16796/ and hence is failing regressions for all other patches. Fixing it up as I type this mail! Shyam ___ Gluster-devel mailing list

[Gluster-devel] Release 3.11: Pending features and reviews (2 days to branching)

Hi, This mail should have been out 3-4 days earlier than now as branching is 2 days away, but hopefully it is not too late. The current release scope can be seen at [1]. If you do *not* recognize your nick in the following list then you can help us out by looking at pending reviews [2] and

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On 04/25/2017 10:08 AM, Shyam wrote: On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote: On Thu, Apr 13, 2017 at 8:17 PM, Shyam > wrote: On 02/28/2017 10:17 AM, Shyam wrote: 1) Halo - Initial Cut (@pranith) Sorry for the delay

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

How this affect CPU usage? Does it read whole file and calculates a hash after it is being written? Will this patch land in 3.10.x? On Tue, Apr 25, 2017 at 10:32 AM, Kotresh Hiremath Ravishankar wrote: > Hi > > https://github.com/gluster/glusterfs/issues/188 is merged in

[Gluster-devel] Statedumps as non-root can not be saved (under /var/run/gluster/...)

Hi, Recently a new ability to trigger statedumps through the Gluster-CLI [0] has been added. This makes it possible to get statedump from applications that use gfapi. By default, statedumps are saved under /var/run/gluster/... and this directory is only writable by root. Applications that use

[Gluster-devel] drop-in management/control panel

Hi, Anyone knows of any solutions I can just drop in my current gluster setup and help me with administrative tasks (create, delete, quota, acl etc) from a web ui? Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On 04/25/2017 03:32 AM, Kotresh Hiremath Ravishankar wrote: Hi https://github.com/gluster/glusterfs/issues/188 is merged in master and needs to go in 3.11 Appropriate github project board updates done, thanks. Further, thanks for noting (in the github issue) that this commit was made before

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On 04/20/2017 02:46 AM, Kaushal M wrote: 2) IPv6 support (@kaushal) This is under review at https://review.gluster.org/16228 . The patch mostly looks fine. The only issue is that it currently depends and links with an internal FB fork of tirpc (mainly for some helper functions and utilities).

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote: On Thu, Apr 13, 2017 at 8:17 PM, Shyam > wrote: On 02/28/2017 10:17 AM, Shyam wrote: 1) Halo - Initial Cut (@pranith) Sorry for the delay in response. Due to some other work

[Gluster-devel] Coverity covscan for 2017-04-25-d6194de9 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-04-25-d6194de9 ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On Thu, Apr 13, 2017 at 8:17 PM, Shyam wrote: > On 02/28/2017 10:17 AM, Shyam wrote: > >> Hi, >> >> With release 3.10 shipped [1], it is time to set the dates for release >> 3.11 (and subsequently 4.0). >> >> This mail has the following sections, so please read or revisit as

Re: [Gluster-devel] fstat problems when killing with stat prefetch turned on

Recently we had worked on some patches to ensure correct stats are returned. https://review.gluster.org/15759 https://review.gluster.org/15659 https://review.gluster.org/16419 Referring to these patches and bugs associated with them might give you some insight into the nature of the problem.

[Gluster-devel] fstat problems when killing with stat prefetch turned on

Hello, I tried reproducing the problem that Mateusz Slupny was experiencing before (stat returning bad st_size value on self-healing) on my own computer with only 3 bricks (one being an arbiter) on 3.10.0. The result with such a small setup was that the bug appeared both on killing and during

Re: [Gluster-devel] finding and fixing memory leaks in xlators

On Tue, Apr 25, 2017 at 02:55:30PM +0530, Amar Tumballi wrote: > Thanks for this detailed Email with clear instructions Niels. > > Can we have this as github issues as well? I don't want this information to > be lost as part of email thread in ML archive. I would like to see if I can > get some

Re: [Gluster-devel] finding and fixing memory leaks in xlators

Thanks for this detailed Email with clear instructions Niels. Can we have this as github issues as well? I don't want this information to be lost as part of email thread in ML archive. I would like to see if I can get some interns to work on these leaks per component as part of their college

[Gluster-devel] finding and fixing memory leaks in xlators

Hi, with the use of gfapi it has become clear that Gluster was never really developed to be loaded in applications. There are many different memory leaks that get exposed through the usage of gfapi. Before, memory leaks were mostly cleaned up automatically because processes would exit. Now, there

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

Hi Serkan, Even though bitrot is not enabled, versioning was being done. As part of it, on every fresh lookup, getxattr calls were made to find weather object is bad, to get it's current version and signature. So a find on gluster mount sometimes would cause high cpu utilization. Since this is

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

Hi https://github.com/gluster/glusterfs/issues/188 is merged in master and needs to go in 3.11 Thanks and Regards, Kotresh H R - Original Message - > From: "Kaushal M" > To: "Shyam" > Cc: gluster-us...@gluster.org, "Gluster Devel"

Re: [Gluster-devel] [Gluster-users] High load on glusterfsd process

Thanks Kotresh. Let me discuss in my team and will let you know. Regards, Abhishek On Tue, Apr 25, 2017 at 12:41 PM, Kotresh Hiremath Ravishankar < khire...@redhat.com> wrote: > Hi Abhishek, > > As this is an enhancement it won't be back ported to 3.7/3.8/3.10 > It would be only available from

Re: [Gluster-devel] [Gluster-users] High load on glusterfsd process

Hi Abhishek, As this is an enhancement it won't be back ported to 3.7/3.8/3.10 It would be only available from upcoming 3.11 release. But I did try applying it to 3.7.6. It has lot of conflicts. If it's important for you, you can upgrade to latest version. available and back port it. If it's