Re: [Gluster-devel] Regression logging on release-3.8-fb branch

On Mon, Jul 17, 2017, at 10:53 PM, Nigel Babu wrote: > >> On Mon, Jul 17, 2017, at 02:00 PM, Jeff Darcy wrote: >>> On Mon, Jul 17, 2017, at 09:28 AM, Nigel Babu wrote: It appears that something changed in https://review.gluster.org/#/c/17771. The tarball with the logs for that patch

Re: [Gluster-devel] Regression logging on release-3.8-fb branch

> On Mon, Jul 17, 2017, at 02:00 PM, Jeff Darcy wrote: > > On Mon, Jul 17, 2017, at 09:28 AM, Nigel Babu wrote: > > It appears that something changed in https://review.gluster.org/#/c/17771. > The tarball with the logs for that patch was 32G. That doesn't sound right. > Is something writing to log

Re: [Gluster-devel] Regression logging on release-3.8-fb branch

On Mon, Jul 17, 2017, at 02:00 PM, Jeff Darcy wrote: > On Mon, Jul 17, 2017, at 09:28 AM, Nigel Babu wrote: >> It appears that something changed in https://review.gluster.org/#/c/17771. >> The tarball with the logs for that patch was 32G. That doesn't sound right. >> Is something writing to

Re: [Gluster-devel] Regression logging on release-3.8-fb branch

On Mon, Jul 17, 2017, at 09:28 AM, Nigel Babu wrote: > It appears that something changed in https://review.gluster.org/#/c/17771. > The tarball with the logs for that patch was 32G. That doesn't sound right. > Is something writing to log excessively after this patch landed? I don't see

Re: [Gluster-devel] GlusterFS v3.12 - Nearing deadline for branch out

hi, Status of the following features targeted for 3.12: 1) Need a way to resolve split-brain (#135) : Mostly will be merged in a day. 2) Halo Hybrid mode (#217): Unfortunately didn't get time to follow up on this, so will not make it to the release. 3) Implement heal throttling (#255):

Re: [Gluster-devel] [Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #162

Ah! sorry, I need to keep this in mind next time when I review. On Mon, Jul 17, 2017 at 6:30 PM, Atin Mukherjee wrote: > kill $pid0 > > kill $pid1 > > EXPECT_WITHIN $CHILD_UP_TIMEOUT "4" ec_child_up_count $V0 0 > > *21:03:33* not ok 17 Got "0" instead of "4",

[Gluster-devel] Regression logging on release-3.8-fb branch

Hi Jeff, It appears that something changed in https://review.gluster.org/#/c/17771. The tarball with the logs for that patch was 32G. That doesn't sound right. Is something writing to log excessively after this patch landed? -- nigelb ___

Re: [Gluster-devel] [Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #162

kill $pid0 kill $pid1 EXPECT_WITHIN $CHILD_UP_TIMEOUT "4" ec_child_up_count $V0 0 *21:03:33* not ok 17 Got "0" instead of "4", LINENUM:40*21:03:33* FAILED COMMAND: 4 ec_child_up_count patchy 0 The failure is quite obvious with brick multiplexing as all the brick instances go down with kill

Re: [Gluster-devel] How to get (and filter) notifications for GitHub issues?

Anyone who's "watching" (has clicked that button on top) the GitHub repo will get notified by email about almost everything (issues, PRs and new comments on them). Without email filters, it'll be a flood of notifications though. https://help.github.com/articles/about-notifications/ On Mon, Jul

Re: [Gluster-devel] Glusto failures with dispersed volumes + Samba

I've retried it more than a couple of times and the failures are consistent. On Wed, Jul 5, 2017 at 6:26 PM, Amar Tumballi wrote: > > > On Wed, Jul 5, 2017 at 6:16 PM, Ashish Pandey wrote: > >> Hi Nigel, >> >> As Pranith has already mentioned, we are

Re: [Gluster-devel] Regarding positioning of nl-cache in gluster client stack

The only requirement on positioning of nl-cache is its good to load it below md-cache. It should be ok to load it between shard and DHT. Regards, Poornima - Original Message - > From: "Pranith Kumar Karampuri" > To: "Krutika Dhananjay" >

Re: [Gluster-devel] Regarding positioning of nl-cache in gluster client stack

On Mon, Jul 17, 2017 at 11:31 AM, Krutika Dhananjay wrote: > Hi Poornima and Pranith, > > I see that currently glusterd loads nl-cache between stat-prefetch and > open-behind on the client stack. Were there any specific considerations for > selecting this position for

[Gluster-devel] Regarding positioning of nl-cache in gluster client stack

Hi Poornima and Pranith, I see that currently glusterd loads nl-cache between stat-prefetch and open-behind on the client stack. Were there any specific considerations for selecting this position for nl-cache? I was interested to see the performance impact of loading this translator between