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

Bug 1460665

Summary:	[disperse] Provide option to control heal load for disperse volume
Product:	[Community] GlusterFS	Reporter:	Ashish Pandey <aspandey>
Component:	disperse	Assignee:	Ashish Pandey <aspandey>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bkunal, bugs, info, nchilaka, pkarampu, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1406363	Environment:
Last Closed:	2018-10-17 09:42:41 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:
Bug Depends On:	1406363
Bug Blocks:	1369781

Comment 1 Ashish Pandey 2017-06-12 11:25:17 UTC

Description of problem: 

We should have a way to control self-heal for a disperse volume. At sometime when we have multiple bricks on a node. If a node goes down and comes up, several brick will start healing. This can lead to very high CPU usage and this can hamper ongoing IO. So we should have a mechanism to control heal, this will help in performing lazy heal during peak time and aggressive heal during less load.

Comment 2 Worker Ant 2017-06-12 11:56:09 UTC

REVIEW: https://review.gluster.org/17521 (syncop : Execute "number" of tasks based on priority) posted (#1) for review on master by Ashish Pandey (aspandey)

Comment 3 Worker Ant 2017-06-28 11:43:20 UTC

REVIEW: https://review.gluster.org/17521 (syncop : Execute "number" of tasks based on priority) posted (#2) for review on master by Ashish Pandey (aspandey)

Comment 4 Ashish Pandey 2018-10-17 09:42:41 UTC

We have come up with a script to control the CPU usage by heal.
That will solve the issue.

https://review.gluster.org/#/c/glusterfs/+/18404/

*** This bug has been marked as a duplicate of bug 1496335 ***