Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1214654

Summary:	Self-heal: Migrate lease_locks as part of self-heal process
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	upcall	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	ndevos, pasik, pgurusid, pkarampu, rtalur, srangana
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-06 07:01:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Soumya Koduri 2015-04-23 10:04:15 UTC

Description of problem:
At present, similar to posix locks, we do not have lease_locks migration support during self-heal process which may lead to data corruption.

Unlike in posix locks case, application(NFS-Ganesha/SMB) clients are not aware of lease_locks taken by the application server, which makes this issue more serious as there could be data corruption without clients know about it.

Maybe we could use the same approach taken to migrate state during rebalance/tiering (BZ1214644). But that will resolve the issue only partially- where in a brick goes down and comes back up again, we can migrate lock state from the active brick process. Later before/during the migration, if the source brick goes down too, we shall lose lock state again.

This bug is to analyze, design and track the changes required to have this support.

Comment 1 Yaniv Kaul 2019-04-28 07:39:52 UTC

Status?

Comment 2 Soumya Koduri 2019-05-06 07:01:16 UTC

This is a Day1 issue (i.e, rebalance and self-healing does not happen for most of the state maintained at the server-side) and there are no plans to address it in the near future. Hence closing the bug.