Re: [Gluster-devel] Changing DISTAF 'global_mode' variable name

On Tue, Jun 21, 2016 at 09:14:58PM +0530, M S Vishwanath Bhat wrote: > On 21 June 2016 at 12:38, shwetha wrote: > > > Hi, > > > > Distaf test framework currently uses a variable 'global_mode' which is for > > selecting the mode in which the tests runs. > > > > When

Re: [Gluster-devel] Reduce memcpy in glfs read and write

Hey Pranith, I am good, I hope you are doing good too. Please find the comments inline. From: Pranith Kumar Karampuri [mailto:pkara...@redhat.com] Sent: Tuesday, June 21, 2016 5:58 AM To: Sachin Pandit Cc: gluster-devel@gluster.org Subject: Re: [Gluster-devel] Reduce

[Gluster-devel] DISTAF- mode of running tests

Hi, Distaf currently has a variable 'global_mode' which is used to select the mode in which the tests runs. When 'global_mode' is set to 'True' we run the tests with the config file configuration and ignores 'runs_on_volumes', 'runs_on_protocols'. When 'global_mode' is set to 'False' we

[Gluster-devel] DISTAF- mode of running tests

Hi, Distaf currently has a variable 'global_mode' which is used to select the mode in which the tests runs. When 'global_mode' is set to 'True' we run the tests with the config file configuration and ignores 'runs_on_volumes', 'runs_on_protocols'. When 'global_mode' is set to 'False' we

[Gluster-devel] Changing DISTAF 'global_mode' variable name

Hi, Distaf test framework currently uses a variable 'global_mode' which is for selecting the mode in which the tests runs. When 'global_mode' is set to 'True' we run the tests with the config file configuration and ignores 'runs_on_volumes', 'runs_on_protocols'. When 'global_mode' is set

Re: [Gluster-devel] Reduce memcpy in glfs read and write

On Wed, Jun 22, 2016 at 5:50 AM, Sachin Pandit wrote: > Hey Pranith, I am good, I hope you are doing good too. > > Please find the comments inline. > > > > *From:* Pranith Kumar Karampuri [mailto:pkara...@redhat.com] > *Sent:* Tuesday, June 21, 2016 5:58 AM > *To:* Sachin

Re: [Gluster-devel] Changing DISTAF 'global_mode' variable name

On 21 June 2016 at 12:38, shwetha wrote: > Hi, > > Distaf test framework currently uses a variable 'global_mode' which is for > selecting the mode in which the tests runs. > > When 'global_mode' is set to 'True' we run the tests with the config file > configuration and

Re: [Gluster-devel] Reduce memcpy in glfs read and write

Would https://bugzilla.redhat.com/show_bug.cgi?id=1233136 be related to Sachin's problem? Milind On 06/21/2016 06:28 PM, Pranith Kumar Karampuri wrote: Hey!! Hope you are doing good. I took a look at the bt. So when flush comes write-behind has to flush all the writes down. I see the

Re: [Gluster-devel] Reduce memcpy in glfs read and write

Hey!! Hope you are doing good. I took a look at the bt. So when flush comes write-behind has to flush all the writes down. I see the following frame hung in iob_unref: Thread 7 (Thread 0x7fa601a30700 (LWP 16218)): #0 0x7fa60cc55225 in pthread_spin_lock () from /lib64/libpthread.so.0

[Gluster-devel] Minutes of today's Gluster Community Bug Triage Meeting

Hi, Thanks a lot everyone for the participation. Here are the minutes of the meeting: Meeting ended Tue Jun 21 12:28:38 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes:

[Gluster-devel] Reduce memcpy in glfs read and write

Hi all, I bid adieu to you all with the hope of crossing path again, and the time has come rather quickly. It feels great to work on GlusterFS again. Currently we are trying to write data backed up by Commvault Simpana to glusterfs volume (Disperse volume). To improve the performance, I have

Re: [Gluster-devel] Question on merging zfs snapshot support into the mainline glusterfs

hi, Is there a plan to come up with an interface for snapshot functionality? For example, in handling different types of sockets in gluster all we need to do is to specify which interface we want to use and ib,network-socket,unix-domain sockets all implement the interface. The code doesn't

Re: [Gluster-devel] How to enable direct io??

There are two things you need to change for o-direct to be handled properly in gluster stack: 1) gluster volume set performance.strict-o-direct on on nfs this option is gluster volume set performance.nfs.strict-o-direct on 2) gluster volume set network.remote-dio off Please note that we

[Gluster-devel] REMINDER: Gluster Community Bug Triage meeting at 12:00 UTC (~in 90 minutes)

Hi all, This meeting is scheduled for anyone that is interested in learning more about, or assisting with the Bug Triage. Meeting details: - location: #gluster-meeting on Freenode IRC (https://webchat.freenode.net/?channels=gluster-meeting ) - date: every Tuesday - time: 12:00 UTC

[Gluster-devel] Bugs with incorrect status

1279747 (mainline) MODIFIED: spec: add CFLAGS=-DUSE_INSECURE_OPENSSL to configure command-line for RHEL-5 only ** mchan...@redhat.com: No change posted, but bug 1279747 is in MODIFIED ** 1338593 (mainline) ASSIGNED: clean posix locks based on client-id as part of server_connection_cleanup

Re: [Gluster-devel] Support for Scaling TIered volume, ie Add/Remove brick and Rebalance

- Original Message - > From: "Atin Mukherjee" > To: "Mohammed Rafi K C" , "Gluster Devel" > > Sent: Tuesday, June 21, 2016 12:34:12 PM > Subject: Re: [Gluster-devel] Support for Scaling TIered volume, ie Add/Remove

Re: [Gluster-devel] Support for Scaling TIered volume, ie Add/Remove brick and Rebalance

I've added my comments in the document. I also feel that getting an user's experience on the command semantics is much required, so mind to open this up in gluster-users ML too? On 06/21/2016 11:31 AM, Mohammed Rafi K C wrote: > Hi, > > The current implementation of Tiering lacks support for

Re: [Gluster-devel] Support for Scaling Tier volume, ie Add/Remove brick and Rebalance

On 06/21/2016 12:05 PM, Hari Gowtham wrote: > > > - Original Message - >> From: "Mohammed Rafi K C" >> To: "Atin Mukherjee" , "Gluster Devel" >> >> Sent: Tuesday, June 21, 2016 11:51:13 AM >> Subject: Re:

[Gluster-devel] Changing DISTAF 'global_mode' variable name

Hi, Distaf test framework currently uses a variable 'global_mode' which is for selecting the mode in which the tests runs. When 'global_mode' is set to 'True' we run the tests with the config file configuration and ignores 'runs_on_volumes', 'runs_on_protocols'. When 'global_mode' is set

Re: [Gluster-devel] Support for Scaling Tier volume, ie Add/Remove brick and Rebalance

- Original Message - > From: "Mohammed Rafi K C" > To: "Atin Mukherjee" , "Gluster Devel" > > Sent: Tuesday, June 21, 2016 11:51:13 AM > Subject: Re: [Gluster-devel] Support for Scaling Tier volume, ie Add/Remove >

Re: [Gluster-devel] Support for Scaling Tier volume, ie Add/Remove brick and Rebalance

On 06/21/2016 11:47 AM, Atin Mukherjee wrote: > The current doc is read-only. Could you please open up the permissions > to add comments? I have changed the permission to read/write. Thanks to Ravi and Atin for pointing this. Rafi > > ~Atin > > On 06/21/2016 11:31 AM, Mohammed Rafi K C wrote:

Re: [Gluster-devel] Support for Scaling TIered volume, ie Add/Remove brick and Rebalance

The current doc is read-only. Could you please open up the permissions to add comments? ~Atin On 06/21/2016 11:31 AM, Mohammed Rafi K C wrote: > Hi, > > The current implementation of Tiering lacks support for rebalance, as > the migration daemon uses the framework for rebalance process. Because

Re: [Gluster-devel] Question on merging zfs snapshot support into the mainline glusterfs

On Mon, Jun 20, 2016 at 5:58 PM, B.K.Raghuram wrote: > Thanks Rajesh, > > I was looking at 3.6 only to check on some locking issues that we were > seeing. > What kind of locking issues you see? If you can provide some more information I can be able to help you. > However, we

[Gluster-devel] Support for Scaling TIered volume, ie Add/Remove brick and Rebalance

Hi, The current implementation of Tiering lacks support for rebalance, as the migration daemon uses the framework for rebalance process. Because of this constraints, we were forced to remove support for add/remove brick on a tired volume. We are now focusing to bring rebalance support along with