- 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 default ?
On Thu, May 30, 2019 at 9:03 A
Hi,
Expected tagging date for release-5.7 is on June, 6th, 2019.
Please ensure required patches are back-ported and also are passing
regressions and are appropriately reviewed for easy merging and tagging
on the date.
--
Regards,
Hari Gowtham.
___
Co
Hi,
Expected tagging date for release-4.1.9 is on June, 4th, 2019.
Please ensure required patches are back-ported and also are passing
regressions and are appropriately reviewed for easy merging and tagging
on the date.
Note: This will be the last release in the 4.1 series as release 7 is
around
On Thu, May 30, 2019 at 9:03 AM Ashish Pandey wrote:
>
>
> I am only concerned about in-service upgrade.
> If a feature/option is not present in V1, then I would prefer not to
> enable it by default on V2.
>
The problem is that without enabling it, (other-)eager-lock will cause
performance issue
I am only concerned about in-service upgrade.
If a feature/option is not present in V1, then I would prefer not to enable it
by default on V2.
We have seen some problem in other-eager-lock when we changed it to enable by
default.
---
Ashish
- Original Message -
From: "Amar Tumba
