Bug 1555261 – After a replace brick command, self-heal takes some time to start healing files on disperse volumes

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1555261 - After a replace brick command, self-heal takes some time to start healing files on disperse volumes

Summary:	After a replace brick command, self-heal takes some time to start healing fil...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	disperse (Show other bugs)
Sub Component:
Version:	3.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Xavi Hernandez
QA Contact:	nchilaka
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1547662
Blocks:	1503137
	Show dependency tree / graph

Reported:	2018-03-14 06:51 EDT by Xavi Hernandez
Modified:	2018-09-04 02:45 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	glusterfs-3.12.2-6
Doc Type:	Bug Fix
Doc Text:	An issue prevented seal-heal to progress causing delays in the heal process after replacing a brick or bringing a failed brick online. This fix keeps self-heal active until all pending files are completely healed.
Story Points:	---
Clone Of:	1547662
Environment:
Last Closed:	2018-09-04 02:44:14 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:2607	None	None	None	2018-09-04 02:45 EDT

Groups: None (edit)

Description Xavi Hernandez 2018-03-14 06:51:28 EDT

+++ This bug was initially created as a clone of Bug #1547662 +++

Description of problem:

After a replace brick, self-heal takes some time to start reconstructing the files, and when it starts, sometimes it pauses for a while.

Version-Release number of selected component (if applicable): mainline


How reproducible:

always

Steps to Reproduce:
1. create a disperse volume
2. replace one brick
3. check new brick contents

Actual results:

New brick is not being filled immediately. It can take some time to start moving files, and it might make pauses.

Expected results:

Self-heal should trigger immediately after replacing the brick and don't stop until finished healing all files.

Additional info:

Comment 6 nchilaka 2018-05-17 09:58:29 EDT

have tested this on 3.12.2-9 and I see selfheal kicks off immediately (as against when tested in 3.8.4-54.9 3.3.1 async, where it take a bit of a delay)
hence moving to verified

Comment 10 errata-xmlrpc 2018-09-04 02:44:14 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2607

Note You need to log in before you can comment on or make changes to this bug.