Re: [Gluster-devel] [Gluster-Maintainers] Please pause merging patches to 3.9 waiting for just one patch

On Thu, Nov 10, 2016 at 1:11 PM, Atin Mukherjee wrote: > > > On Thu, Nov 10, 2016 at 1:04 PM, Pranith Kumar Karampuri > wrote: >> >> I am trying to understand the criticality of these patches. Raghavendra's >> patch is crucial because gfapi workloads(for

Re: [Gluster-devel] [Gluster-Maintainers] Please pause merging patches to 3.9 waiting for just one patch

On Thu, Nov 10, 2016 at 1:04 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > I am trying to understand the criticality of these patches. Raghavendra's > patch is crucial because gfapi workloads(for samba and qemu) are affected > severely. I waited for Krutika's patch because VM

Re: [Gluster-devel] [Gluster-Maintainers] Please pause merging patches to 3.9 waiting for just one patch

I am trying to understand the criticality of these patches. Raghavendra's patch is crucial because gfapi workloads(for samba and qemu) are affected severely. I waited for Krutika's patch because VM usecase can lead to disk corruption on replace-brick. If you could let us know the criticality and

Re: [Gluster-devel] [Gluster-users] Feedback on DHT option "cluster.readdir-optimize"

On Thu, Nov 10, 2016 at 12:58 PM, Gandalf Corvotempesta < gandalf.corvotempe...@gmail.com> wrote: > Il 10 nov 2016 08:22, "Raghavendra > ha scritto: > > > > Kyle, > > > > Thanks for your your response :). This really helps. From 13s to 0.23s > seems like huge

Re: [Gluster-devel] [Gluster-users] Feedback on DHT option "cluster.readdir-optimize"

Il 10 nov 2016 08:22, "Raghavendra ha scritto: > > Kyle, > > Thanks for your your response :). This really helps. From 13s to 0.23s seems like huge improvement. >From 13 minutes to 23 seconds, not from 13 seconds :) ___

Re: [Gluster-devel] [Gluster-Maintainers] Please pause merging patches to 3.9 waiting for just one patch

Pranith, I'd like to see following patches getting in: http://review.gluster.org/#/c/15722/ http://review.gluster.org/#/c/15714/ http://review.gluster.org/#/c/15792/ On Thu, Nov 10, 2016 at 7:12 AM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi, > The only problem left was

Re: [Gluster-devel] [Gluster-users] Feedback on DHT option "cluster.readdir-optimize"

Kyle, Thanks for your your response :). This really helps. From 13s to 0.23s seems like huge improvement. regards, Raghavendra On Tue, Nov 8, 2016 at 8:21 PM, Kyle Johnson wrote: > Hey there, > > We have a number of processes which daily walk our entire directory tree >

[Gluster-devel] Please pause merging patches to 3.9 waiting for just one patch

hi, The only problem left was EC taking more time. This should affect small files a lot more. Best way to solve it is using compound-fops. So for now I think going ahead with the release is best. We are waiting for Raghavendra Talur's http://review.gluster.org/#/c/15778 before going ahead

Re: [Gluster-devel] [Gluster-users] Feedback on DHT option "cluster.readdir-optimize"

Hey there, We have a number of processes which daily walk our entire directory tree and perform operations on the found files. Pre-gluster, this processes was able to complete within 24 hours of starting. After outgrowing that single server and moving to a gluster setup (two bricks, two

Re: [Gluster-devel] Weekly Community Meeting - 2016-11-09

On Wed, Nov 9, 2016 at 9:55 AM, Kaushal M wrote: > On Wed, Nov 9, 2016 at 9:54 AM, Kaushal M wrote: >> Hi all, >> This a reminder to everyone to add the updates to the meeting etherpad >> [1] before the meeting starts at 1200UTC today. > > Also, add any

Re: [Gluster-devel] getting "Transport endpoint is not connected" in glusterfs mount log file.

could anyone reply on this. On Wed, Nov 9, 2016 at 11:08 AM, ABHISHEK PALIWAL wrote: > Hi, > > We could see that sync is getting failed to sync the GlusterFS bricks due > to error trace "Transport endpoint is not connected " > > [2016-10-31 04:06:03.627395] E [MSGID: