Bug 798907

Summary:	Make synctask scalable
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	core	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shwetha Panduranga <shwetha.h.panduranga>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	pre-release	CC:	gluster-bugs, vbellur, vraman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 18:00:53 UTC	Type:	---
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:
Bug Blocks:	817967

Description Pranith Kumar K 2012-03-01 08:54:07 UTC

Description of problem:
At the moment, synctask uses task->frame to perform all the syncops, this will lead to high-memory usage if the task crawls millions of directories. i.e millions of STACK_WINDS/UNWINDS.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Amar Tumballi 2012-03-02 04:16:36 UTC

patch submitted already... yet to be merged

Comment 2 Anand Avati 2012-03-10 06:19:38 UTC

CHANGE: http://review.gluster.com/2850 (syncop: Make syntask scalable) merged in master by Vijay Bellur (vijay)

Comment 3 Anand Avati 2012-03-18 07:53:31 UTC

CHANGE: http://review.gluster.com/2902 (libglusterfs: Destroy stack_lock in STACK_DESTROY) merged in release-3.2 by Anand Avati (avati)

Comment 4 Shwetha Panduranga 2012-06-04 09:08:49 UTC

Test case:-
------------
1. create a replicate volume(1x3)
2. bring down 2 bricks
3. Create fuse/nfs mount
4. Create files ( 1 million files. files of different sizes )
5. Bring back the bricks.
6. execute "gluster volume heal <volume_name> full"

Expected Output:-
-----------------------
The memory consumption by glustershd process should not shoot up.

Comment 5 Shwetha Panduranga 2012-06-06 07:13:33 UTC

Verified the fix on 3.3.0qa45. Bug is fixed.