t;> - Original Message -
>> > From: "Richard Wareing" <rware...@fb.com>
>> > To: "Pranith Kumar Karampuri" <pkara...@redhat.com>
>> > Cc: gluster-devel@gluster.org
>> > Sent: Monday, January 25, 2016 8:17:11 AM
>&g
[raghavendra...@gmail.com] on behalf of
Raghavendra G [raghaven...@gluster.com]
Sent: Tuesday, January 26, 2016 9:49 PM
To: Raghavendra Gowdappa
Cc: Richard Wareing; Gluster Devel
Subject: Re: [Gluster-devel] Feature: Automagic lock-revocation for
features/locks xlator (v3.7.x)
On Mon, Jan 25, 2016
ster-devel@gluster.org
> > Sent: Monday, January 25, 2016 8:17:11 AM
> > Subject: Re: [Gluster-devel] Feature: Automagic lock-revocation for
> features/locks xlator (v3.7.x)
> >
> > Yup per domain would be useful, the patch itself currently honors
> domains as
> >
lly understood by developers.
Richard
From: Venky Shankar [yknev.shan...@gmail.com]
Sent: Sunday, January 24, 2016 9:36 PM
To: Pranith Kumar Karampuri
Cc: Richard Wareing; Gluster Devel
Subject: Re: [Gluster-devel] Feature: Automagic lock-revocation for
feat
On 01/25/2016 02:17 AM, Richard Wareing wrote:
Hello all,
Just gave a talk at SCaLE 14x today and I mentioned our new locks
revocation feature which has had a significant impact on our GFS
cluster reliability. As such I wanted to share the patch with the
community, so here's the bugzilla
Yup per domain would be useful, the patch itself currently honors domains as
well. So locks in a different domains will not be touched during revocation.
In our cases we actually prefer to pull the plug on SHD/DHT domains to ensure
clients do not hang, this is important for DHT self heals
Hello all,
Just gave a talk at SCaLE 14x today and I mentioned our new locks revocation
feature which has had a significant impact on our GFS cluster reliability. As
such I wanted to share the patch with the community, so here's the bugzilla
report:
