Le lundi 25 janvier 2016 à 22:24 +0100, Niels de Vos a écrit :
> On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote:
> > Hi,
> >
> > so today, after fixing one last config item, the smoke test jobs run
> > fine on the Centos 6 builder in the RH DC, which build things as non
> > root,
Hi Pranith,
On 26/01/16 03:47, Pranith Kumar Karampuri wrote:
hi,
Traditionally gluster has been using ctime/mtime of the
files/dirs on the bricks as stat output. Problem we are seeing with this
approach is that, software which depends on it gets confused when there
are differences in the
On Tue, Jan 26, 2016 at 03:11:50AM +, Richard Wareing wrote:
> > If there is one bucket per client and one thread per bucket, it would be
> > difficult to scale as the number of clients increase. How can we do this
> > better?
>
> On this note... consider that 10's of thousands of clients are
On 01/25/16 20:36, Pranith Kumar Karampuri wrote:
On 01/26/2016 08:41 AM, Richard Wareing wrote:
If there is one bucket per client and one thread per bucket, it
would be
difficult to scale as the number of clients increase. How can we do
this
better?
On this note... consider that 10's of t
On 01/25/16 18:24, Ravishankar N wrote:
On 01/26/2016 01:22 AM, Shreyas Siravara wrote:
Just out of curiosity, what benefits do we think this throttling
xlator would provide over the "enable-least-priority" option (where
we put all the fops from SHD, etc into a least pri queue)?
For one,
On 01/26/2016 08:41 AM, Richard Wareing wrote:
If there is one bucket per client and one thread per bucket, it would be
difficult to scale as the number of clients increase. How can we do this
better?
On this note... consider that 10's of thousands of clients are not unrealistic
in production
Addition case on ctime,
1. When we do internal operations like rebalance, tier-migration, afr-heal etc
ctime time changes, this is not desirable as its a internal fop
2. For a compliance case(WORM-Retenetion), ctime change means there is
something that has changes on a READ-ONLY file, which is b
On 01/26/2016 08:14 AM, Vijay Bellur wrote:
On 01/25/2016 12:36 AM, Ravishankar N wrote:
Hi,
We are planning to introduce a throttling xlator on the server (brick)
process to regulate FOPS. The main motivation is to solve complaints
about
AFR selfheal taking too much of CPU resources. (due
> If there is one bucket per client and one thread per bucket, it would be
> difficult to scale as the number of clients increase. How can we do this
> better?
On this note... consider that 10's of thousands of clients are not unrealistic
in production :). Using a thread per bucket would also be
hi,
Traditionally gluster has been using ctime/mtime of the
files/dirs on the bricks as stat output. Problem we are seeing with this
approach is that, software which depends on it gets confused when there
are differences in these times. Tar especially gives "file changed as we
read it" w
On 01/25/2016 12:36 AM, Ravishankar N wrote:
Hi,
We are planning to introduce a throttling xlator on the server (brick)
process to regulate FOPS. The main motivation is to solve complaints about
AFR selfheal taking too much of CPU resources. (due to too many fops for
entry
self-heal, rchecksums
On 01/26/2016 01:22 AM, Shreyas Siravara wrote:
Just out of curiosity, what benefits do we think this throttling xlator would provide
over the "enable-least-priority" option (where we put all the fops from SHD,
etc into a least pri queue)?
For one, it could provide more granularity on th
On 01/22/2016 09:13 AM, Raghavendra Talur wrote:
HI All,
I am sure there are many tricks hidden under sleeves of many Gluster
developers.
I realized this when speaking to new developers. It would be good have a
searchable thread of such tricks.
Just reply back on this thread with the tricks tha
The Linux Foundation's Vault
(http://events.linuxfoundation.org/events/vault ) event focusing on
Linux storage and filesystems currently has their call for papers open
- but it closes this Friday, January 29th. I'm highlighting this
because GlusterFS is mentioned as a suggested topic!
This year, i
On Mon, Jan 25, 2016 at 10:24:33PM +0100, Niels de Vos wrote:
> On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote:
> > Hi,
> >
> > so today, after fixing one last config item, the smoke test jobs run
> > fine on the Centos 6 builder in the RH DC, which build things as non
> > root, t
Hey Hey Panith,
>Maybe give clients a second (or more) chance to "refresh" their locks - in the
>sense, when a lock is about to be revoked, notify the client which can then
>call for a refresh to conform it's locks holding validity. This would require
>some maintainance work on the client to ke
On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote:
> Hi,
>
> so today, after fixing one last config item, the smoke test jobs run
> fine on the Centos 6 builder in the RH DC, which build things as non
> root, then start the tests, then reboot the server.
Nice, sounds like great prog
Here are the results of "rsync" test. I've got 2 volumes — source and target —
performing multiple files rsyncing from one volume to another.
Source volume:
===
root 22259 3.5 1.5 1204200 771004 ? Ssl Jan23 109:42 /usr/sbin/
glusterfs --volfile-server=glusterfs.example.com --volfile-
On Fri, Jan 22, 2016 at 9:29 AM, Niels de Vos wrote:
> On Mon, Jan 18, 2016 at 07:46:16PM -0800, Amye Scavarda wrote:
>> We're kicking off an updated Monthly Newsletter, coming out mid-month.
>> We'll highlight special posts, news and noteworthy threads from the
>> mailing lists, events, and other
Just out of curiosity, what benefits do we think this throttling xlator would
provide over the "enable-least-priority" option (where we put all the fops from
SHD, etc into a least pri queue)?
> On Jan 25, 2016, at 12:29 AM, Venky Shankar wrote:
>
> On Mon, Jan 25, 2016 at 01:08:38PM +0530, R
On Mon, Jan 25, 2016 at 11:29 PM, Michael Scherer
wrote:
> Hi,
>
> so today, after fixing one last config item, the smoke test jobs run
> fine on the Centos 6 builder in the RH DC, which build things as non
> root, then start the tests, then reboot the server.
>
Awesome!
>
> Now, I am looking
Hi,
so today, after fixing one last config item, the smoke test jobs run
fine on the Centos 6 builder in the RH DC, which build things as non
root, then start the tests, then reboot the server.
Now, I am looking at the fedora one, but once this one is good, I will
likely reinstall a few builders
Le lundi 25 janvier 2016 à 15:41 +0100, Michael Scherer a écrit :
> Hi,
>
> in order to fix some issues (I hope), I am gonna start a reindex of the
> lucense DB of gerrit. This requires the server to be put offline for a
> while, and I did a test on another VM, would take ~10 minutes (it was
> 240
- Original Message -
From: "Jeff Darcy"
To: "Richard Wareing"
Cc: "Gluster Devel"
Sent: Monday, January 25, 2016 7:27:20 PM
Subject: Re: [Gluster-devel] Tips and Tricks for Gluster Developer
Oh boy, here we go. ;)
I second Richard's suggestion to use cscope or some equivalent. It's a
Hi,
in order to fix some issues (I hope), I am gonna start a reindex of the
lucense DB of gerrit. This requires the server to be put offline for a
while, and I did a test on another VM, would take ~10 minutes (it was
240 seconds on the VM, but it was likely faster since the VM is faster)
I will t
Oh boy, here we go. ;)
I second Richard's suggestion to use cscope or some equivalent. It's a good
idea in general, but especially with a codebase as large and complex as
Gluster's. I literally wouldn't be able to do my job without it. I also have
a set of bash/zsh aliases that will regener
- Original Message -
> From: "Niels de Vos"
> To: "Rajesh Joseph"
> Cc: "Richard Wareing" , "Gluster Devel"
>
> Sent: Monday, January 25, 2016 6:30:53 PM
> Subject: Re: [Gluster-devel] Tips and Tricks for Gluster Developer
>
> On Mon, Jan 25, 2016 at 06:41:50AM -0500, Rajesh Joseph w
On Mon, Jan 25, 2016 at 06:41:50AM -0500, Rajesh Joseph wrote:
>
>
> - Original Message -
> > From: "Richard Wareing"
> > To: "Raghavendra Talur"
> > Cc: "Gluster Devel"
> > Sent: Monday, January 25, 2016 8:12:53 AM
> > Subject: Re: [Gluster-devel] Tips and Tricks for Gluster Developer
- Original Message -
> From: "Richard Wareing"
> To: "Raghavendra Talur"
> Cc: "Gluster Devel"
> Sent: Monday, January 25, 2016 8:12:53 AM
> Subject: Re: [Gluster-devel] Tips and Tricks for Gluster Developer
>
> Here's my tips:
>
> 1. General C tricks
> - learn to use vim or emacs &
I don't like installing the bits under /usr/local so I configure and
compile them to install in the same place as a Fedora rpm would.
Here is my compile command
./autogen.sh
CFLAGS="-g -O0 -Werror -Wall -Wno-error=cpp -Wno-error=maybe-uninitialized"
./configure \
--prefix=/usr \
On Mon, Jan 25, 2016 at 01:08:38PM +0530, Ravishankar N wrote:
> On 01/25/2016 12:56 PM, Venky Shankar wrote:
> >Also, it would be beneficial to have the core TBF implementation as part of
> >libglusterfs so as to be consumable by the server side xlator component to
> >throttle dispatched FOPs and
the client statedump is at http://pastebin.centos.org/38671/
On Mon, Jan 25, 2016 at 3:33 PM, baul jianguo wrote:
> 3.5.7 also hangs.only the flush op hung. Yes,off the
> performance.client-io-threads ,no hang.
>
> The hang does not relate the client kernel version.
>
> One client statdump about
32 matches
Mail list logo