Re: [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-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-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

[Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #2040

See -- [...truncated 15600 lines...] ./tests/bugs/glusterd/bug-1367478-volume-start-validation-after-glusterd-restart.t - 25 second

[Gluster-Maintainers] 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

[Gluster-Maintainers] FB: Branch creation

All, We (Jeff, Vijay, Amye, and Myself) have been in conversations with FB folks over upstreaming their work and also around helping them catch upto 3.8 (as they are on 3.6.3 + large number of patches (say ~300)). Towards this, to ease their movement to the 3.8 release, considering the