[Gluster-devel] Gluster Infra Updates - July

Hello folks, We'll be sending updates about the state of the infrastructure and what's been going on every month from now on. Here's the update for July What's Been Going on In Gluster Infra # Gerrit * We've updated how the review flags work. When you rebase a change or you update the commit

[Gluster-devel] Gro-replication may fail after using glfsapi to create and write a file with gluster3.7.13

Hi all, I did some experiments on geo-replication. # gluster volume info Source site: Volume Name: source Type: Disperse Volume ID: 1b6f0353-b4f2-4a1e-9f4a-157e90dafc07 Status: Started Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: giting1:/export/sor_bk1/fs Brick2:

[Gluster-devel] CTDB support in gdeploy

Hi, I have Improved CTDB support in gdeploy and have committed to master. Now we will be able to setup ctdb end-to-end on a minimal RHEL/Fedora machine. gdeploy subscribes to necessary channels and installs the packages and configures ctdb. Please find the attached configuration file. Fixes are

[Gluster-devel] GlusterFS-v3.7.14 tagging approaching

Hi all, 3.7.14 is scheduled to be tagged on the 30th of this month (30/Jul/2016), ie. in 3 more days. Please ensure that you get the required changes merged by 1200 UTC on the 30th. We have a good amount of fixes already with 18 commits into release-3.7 since 3.7.13. Make sure to add bugs for

Re: [Gluster-devel] [Gluster-users] 3.7.13 & proxmox/qemu

On Tue, Jul 26, 2016 at 9:38 PM, Krutika Dhananjay wrote: > Yes please, could you file a bug against glusterfs for this issue? > https://bugzilla.redhat.com/show_bug.cgi?id=1360785 > > > -Krutika > > On Wed, Jul 27, 2016 at 1:39 AM, David Gossage < >

[Gluster-devel] Weekly Community Meeting - 27/Jul/2016

We had a pretty well attended and lively meeting today, thanks to everyone who attended. The meeting minutes and logs are available at the links below. Minutes: https://meetbot.fedoraproject.org/gluster-meeting/2016-07-27/weekly_community_meeting_27jul2016.2016-07-27-12.02.html Minutes (text):

Re: [Gluster-devel] Review request for md-cache enhancements

On Wed, Jul 27, 2016 at 06:20:48AM -0400, Poornima Gurusiddaiah wrote: > Hi, > > Here is a patch http://review.gluster.org/#/c/15002 that lets md-cache > inform upcall about the list of xattrs, that it is interested, in > receiving invalidations. Could you please take a look at this. There > are

Re: [Gluster-devel] fail-over taking too long when a node reboots

On Wed, Jul 27, 2016 at 12:40:58PM +0530, Pranith Kumar Karampuri wrote: > hi, > Does anyone have complete understanding of keepalive timeout vs TCP > User timeout (UTO) options? For both afr and EC when the server reboots it > takes 42 seconds for the fops to fail with ENOTCONN >

Re: [Gluster-devel] [Gluster-users] Need a way to display and flush gluster cache ?

On Wed, Jul 27, 2016 at 10:29 AM, Mohammed Rafi K C wrote: > Thanks for your feedback. > > In fact meta xlator is loaded only on fuse mount, is there any particular > reason to not to use meta-autoload xltor for nfs server and libgfapi ? > I think its because of lack of

Re: [Gluster-devel] One client can effectively hang entire gluster array

I've filed a bug on the issue at: https://bugzilla.redhat.com/show_bug.cgi?id=1360689 On Fri, Jul 15, 2016 at 12:44 PM, Raghavendra G wrote: > Hi Patrick, > > Is it possible to test out whether the patch fixes your issue? There is > nothing like validation from user

[Gluster-devel] Review request for md-cache enhancements

Hi, Here is a patch http://review.gluster.org/#/c/15002 that lets md-cache inform upcall about the list of xattrs, that it is interested, in receiving invalidations. Could you please take a look at this. There are dependent patches on this, which i will work on based on the review comments.

Re: [Gluster-devel] [Gluster-users] Need a way to display and flush gluster cache ?

On Wed, Jul 27, 2016 at 10:29:37AM +0530, Mohammed Rafi K C wrote: > Thanks for your feedback. > > In fact meta xlator is loaded only on fuse mount, is there any > particular reason to not to use meta-autoload xltor for nfs server and > libgfapi ? I have no idea what the reason could be.

[Gluster-devel] fail-over taking too long when a node reboots

hi, Does anyone have complete understanding of keepalive timeout vs TCP User timeout (UTO) options? For both afr and EC when the server reboots it takes 42 seconds for the fops to fail with ENOTCONN (saved_frames_unwind()). I am wondering if there is any way to reduce this time by playing