Bug 1097041

Summary:	Use thread pool in libgfchangelog in history changelog processing
Product:	[Community] GlusterFS	Reporter:	Venky Shankar <vshankar>
Component:	core	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-24 09:21:28 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 Venky Shankar 2014-05-13 04:08:52 UTC

Description of problem:
Currently during processing of historical journals (using history API), the background processing of changelogs is sub optimal. A thread is spawned for each changelog that needs to be processed. This setup and teardown should be avoided by using a pool of threads for background changelog processing.


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

Comment 2 Amar Tumballi 2018-10-24 09:21:28 UTC

We will pick these optimizations as part of https://github.com/gluster/glusterfs/issues/532