[Gluster-devel] Glusterfs 3.10.3 has been tagged

Glusterfs 3.10.3 has been tagged. Packages for the various distributions will be available in a few days, and with that a more formal release announcement will be made. - Tagged code: https://github.com/gluster/glusterfs/tree/v3.10.3 - Release notes:

Re: [Gluster-devel] Empty info file preventing glusterd from starting

On Wed, May 31, 2017 at 04:08:06PM +0530, ABHISHEK PALIWAL wrote: > We are using 3.7.6 and on link https://review.gluster.org/#/c/16279 status > is "can't merge" Note that 3.7.x will not get any updates anymore. We currently maintain version 3.8.x, 3.10.x and 3.11.x. See the release schedele for

[Gluster-devel] Coverity covscan for 2017-05-31-57b0a4a3 (master branch)

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

Re: [Gluster-devel] Empty info file preventing glusterd from starting

So is there any one working on it to fix this issue either by this patch or some other way? if yes then please provide the time plan. On Wed, May 31, 2017 at 4:25 PM, Amar Tumballi wrote: > > > On Wed, May 31, 2017 at 4:08 PM, ABHISHEK PALIWAL >

Re: [Gluster-devel] Empty info file preventing glusterd from starting

On Wed, May 31, 2017 at 4:08 PM, ABHISHEK PALIWAL wrote: > We are using 3.7.6 and on link https://review.gluster.org/#/c/16279 > status is "can't merge" > > On Wed, May 31, 2017 at 4:05 PM, Amar Tumballi > wrote: > >> This is already part of 3.11.0

Re: [Gluster-devel] Empty info file preventing glusterd from starting

We are using 3.7.6 and on link https://review.gluster.org/#/c/16279 status is "can't merge" On Wed, May 31, 2017 at 4:05 PM, Amar Tumballi wrote: > This is already part of 3.11.0 release? > > On Wed, May 31, 2017 at 3:47 PM, ABHISHEK PALIWAL >

[Gluster-devel] Making efficient use of conditional variables

hi, I just read the pdf linked in the patch https://review.gluster.org/16832 and learned something I didn't know before about how to use conditional variables efficiently. Just wanted to share it here in case it is useful for others too. Do go through the patch as well to see how the idea is

Re: [Gluster-devel] Empty info file preventing glusterd from starting

This is already part of 3.11.0 release? On Wed, May 31, 2017 at 3:47 PM, ABHISHEK PALIWAL wrote: > Hi Atin, > > Could you please let us know any time plan for deliver of this patch. > > Regards, > Abhishek > > On Tue, May 9, 2017 at 6:37 PM, ABHISHEK PALIWAL

Re: [Gluster-devel] Empty info file preventing glusterd from starting

Hi Atin, Could you please let us know any time plan for deliver of this patch. Regards, Abhishek On Tue, May 9, 2017 at 6:37 PM, ABHISHEK PALIWAL wrote: > Actually it is very risky if it will reproduce in production thats is why > I said it is on high priority as want

Re: [Gluster-devel] Volgen support for loading trace and io-stats translators at specific points in the graph

I just realised there was already some effort in 2010 to have per-xl latency measurement. See commit d90c2f86ca7a8f6660e98da1e48c4798539b7d51. Turns out you need to send SIGUSR2 to the process to enable it. And the stats are collected through statedump. Haven't yet tested it. Will try and get

Re: [Gluster-devel] Volgen support for loading trace and io-stats translators at specific points in the graph

On Tue, May 30, 2017 at 6:42 PM, Shyam wrote: > On 05/30/2017 05:28 AM, Krutika Dhananjay wrote: > >> You're right. With brick graphs, this will be a problem. >> >> Couple of options: >> >> 1. To begin with we identify points where we think it would be useful to >> load