- Original Message -
From: "Xavi Hernandez"
To: "Ashish Pandey"
Cc: "Amar Tumballi Suryanarayan" , "gluster-devel"
Sent: Thursday, May 30, 2019 2:03:54 PM
Subject: Re: [Gluster-devel] Should we enable features.locks-notify.contention
by
missing something ?
> ---
> Ashish
>
> --
> *From: *"Amar Tumballi Suryanarayan"
> *To: *"Xavi Hernandez"
> *Cc: *"gluster-devel"
> *Sent: *Thursday, May 30, 2019 12:04:43 PM
> *Subject: *Re: [Gluster-devel] Should we e
;Amar Tumballi Suryanarayan"
To: "Xavi Hernandez"
Cc: "gluster-devel"
Sent: Thursday, May 30, 2019 12:04:43 PM
Subject: Re: [Gluster-devel] Should we enable features.locks-notify.contention
by default ?
On Thu, May 30, 2019 at 11:34 AM Xavi Hernandez < xhernan..
On Thu, May 30, 2019 at 11:34 AM Xavi Hernandez
wrote:
> Hi all,
>
> a patch [1] was added some time ago to send upcall notifications from the
> locks xlator to the current owner of a granted lock when another client
> tries to acquire the same lock (inodelk or entrylk). This makes it possible
>
Hi all,
a patch [1] was added some time ago to send upcall notifications from the
locks xlator to the current owner of a granted lock when another client
tries to acquire the same lock (inodelk or entrylk). This makes it possible
to use eager-locking on the client side, which improves performance
