[Gluster-devel] conflicting keys for option eager-lock

[Ravishankar N]

On 04/09/2016 07:55 AM, Vijay Bellur wrote:
> Hey Pranith, Ashish -
>
> We have broken support for group virt after the following commit in 
> release-3.7:

Just nit-picking, eager-lock is ON by default for replicate volumes, so 
it is not a deal breaker unless some one explicitly disables the option 
before enabling the virt-profile  settings. Nevertheless , it would be 
good to have for 3.7.11 as users have already noticed the issue 
(https://www.mail-archive.com/users@ovirt.org/msg32043.html). If we're 
waiting to get this in, I would once again request also taking the 
arbiter fix (http://review.gluster.org/#/c/13925) also in. The change is 
unobtrusive but fixes a rather bad performance issue for arbiter volumes.

Thanks,
Ravi


>
> commit 46920e3bd38d9ae7c1910d0bd83eff309ab20c66
> Author: Ashish Pandey <aspandey at redhat.com>
> Date:   Fri Mar 4 13:05:09 2016 +0530
>
>     cluster/ec: Provide an option to enable/disable eager lock
>
>
> I have sent a patch to address this on master [1]. We would need to 
> backport this patch to release-3.7 once merged on master and include 
> it in 3.7.11.
>
> Kaushal - please hold tagging of 3.7.11 as there is an undesirable 
> impact on oVirt & OpenStack workflows if we
> don't include this patch.
>
> Thanks,
> Vijay
>
> [1] http://review.gluster.org/#/c/13929
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel