Re: [Gluster-devel] [Gluster-users] 120k context switches on GlsuterFS nodes

On 05/17/2017 11:07 PM, Pranith Kumar Karampuri wrote: + gluster-devel On Wed, May 17, 2017 at 10:50 PM, mabi > wrote: I don't know exactly what kind of context-switches it was but what I know is that it is the "cs" number under "system"

[Gluster-devel] Release 3.11: Rc1 and release tagging dates

Hi, We have had a steady stream of backports to 3.11 and hence will tag RC1 around May-22nd and will do the final release tagging around May-29th. Post RC1 that gives exactly one week to get any critical bug fixes into the code base, so be aware of those dates, and also mark any blockers

Re: [Gluster-devel] Release 3.12 and 4.0: Thoughts on scope

A short reminder on dates for these releases: 3.12 is targeted around Aug-30 4.0 is targeted around Nov-30 These are tracked as milestones in github and the dates reflected appropriately there [1]. Further the community webpage is updated to point to the github pages to keep ambiguity out of

[Gluster-devel] Weekly GlusterFS Untriaged Bugs Report

Weekly GlusterFS Untriaged Bugs Report 1450567 / core: brick process cannot be started at the first time 1449416 / core: errno used incorrectly or misleadingly in error messages 1449861 / core: glusterd-geo-rep.c doesn't log stderr on failure to execute subprocesses 1450593 / core: Gluster

Re: [Gluster-devel] [Gluster-users] 120k context switches on GlsuterFS nodes

+ gluster-devel On Wed, May 17, 2017 at 10:50 PM, mabi wrote: > I don't know exactly what kind of context-switches it was but what I know > is that it is the "cs" number under "system" when you run vmstat. > > Also I use the percona linux monitoring template for cacti ( >

[Gluster-devel] Coverity covscan for 2017-05-17-2592fa04 (master branch)

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

Re: [Gluster-devel] tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t - regression failures

On Wed, May 17, 2017 at 4:34 PM, Ravishankar N wrote: > On 05/17/2017 04:09 PM, Pranith Kumar Karampuri wrote: > > karthik, Ravi, > What is the plan to bring it back? Did you guys find RC for the > failure? > > Are you referring to

Re: [Gluster-devel] Change in rebalance graph

AFR had similar problem 2 years back and we started persisting afr children and graph always gets generated with what the xattrs will be in that order as an option. You can check afr_pending_xattrs_init() for it. On the glusterd side we give an identifer for each of the bricks. The main reason we

Re: [Gluster-devel] tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t - regression failures

On 05/17/2017 04:09 PM, Pranith Kumar Karampuri wrote: karthik, Ravi, What is the plan to bring it back? Did you guys find RC for the failure? Are you referring to gfid-mismatch-resolution-with-fav-child-policy.t? I already mentioned the RCA in the patch I linked to earlier in this

Re: [Gluster-devel] Suggestion to optimize posix_getxattr call

yeah +1 from me too. On Mon, May 15, 2017 at 2:56 PM, Mohit Agrawal wrote: > Hi, > > I was just checking of posix_getxattr code to debug of my one problem.I > have found scope of improvement in > this function to execute system call in better way.As of now >

Re: [Gluster-devel] tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t - regression failures

karthik, Ravi, What is the plan to bring it back? Did you guys find RC for the failure? On Mon, May 15, 2017 at 10:52 AM, Ravishankar N wrote: > On 05/12/2017 03:33 PM, Atin Mukherjee wrote: > > tests/basic/afr/add-brick-self-heal.t >