Bug 1332523 - do not allow cluster.eager-lock option to be enabled on EC volume
Summary: do not allow cluster.eager-lock option to be enabled on EC volume
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 11:48 UTC by Nag Pavan Chilakam
Modified: 2019-04-03 09:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-06 14:17:21 UTC
Embargoed:

Attachments (Terms of Use)

Description Nag Pavan Chilakam 2016-05-03 11:48:33 UTC 
we have disperse.eager-lock option for enabling eager lock on EC volume.
We need to disallow enabling cluster.eager-lock on an EC volume as it is meant for AFR volume

As there is no impact functionally, raising a low severity bug for tracking this


version:3.7.9-2
Comment 4 Atin Mukherjee 2016-05-05 13:42:59 UTC 
Wait a second! I think I misunderstood the problem.

Pranith,

Can't we add a validate_fn in volume map entry table for disperse.eager-lock to check like if volume type is disperse then allow it, otherwise not?
Note You need to log in before you can comment on or make changes to this bug.