Bug 1097041 - Use thread pool in libgfchangelog in history changelog processing
Summary: Use thread pool in libgfchangelog in history changelog processing
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Venky Shankar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-13 04:08 UTC by Venky Shankar
Modified: 2018-10-24 09:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-24 09:21:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.