Bug 1104459

Summary: RFC: make epoll multithreaded
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: ssamanta
Component: glusterdAssignee: Vijaikumar Mallikarjuna <vmallika>
Status: CLOSED ERRATA QA Contact: Ben Turner <bturner>
Severity: low Docs Contact:
Priority: urgent    
Version: rhgs-3.0CC: annair, bmohanra, kparthas, mzywusko, nlevinki, nsathyan, rcyriac, rhinduja, rjoseph, sasundar, smohan, srangana, ssamanta, vagarwal, vbellur, vmallika
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.0.4   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.6.0.48-1 Doc Type: Enhancement
Doc Text:
Previously, epoll thread did socket even-handling and the same thread was used for serving the client or processing the response received from the server. Due to this, other requests were in a queue untill the current epoll thread completed its operation. With multi-threaded epoll, events are distributed that improves the performance due the parallel processing of requests/responses received.
Story Points: ---
Clone Of: 1096729
: 1104462 (view as bug list) Environment:
Last Closed: 2015-03-26 06:34:13 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: 1096729, 1193995, 1194525, 1196956    
Bug Blocks: 1088355, 1097224, 1098021, 1098025, 1104462, 1182947    

Comment 2 Vijaikumar Mallikarjuna 2014-06-10 07:37:51 UTC
We need to change the epoll thread model and make it lighter.

http://review.gluster.com/3842 is one such approach.

Comment 8 Ben Turner 2015-03-19 17:05:06 UTC
Verified on 3.6.0.53.

Comment 9 Bhavana 2015-03-24 03:45:20 UTC
Hi vijai,


The doc text is updated. review the same and sign off if it looks ok.

Comment 10 Vijaikumar Mallikarjuna 2015-03-24 05:28:48 UTC
doc text looks good to me

Comment 12 errata-xmlrpc 2015-03-26 06:34:13 UTC
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://rhn.redhat.com/errata/RHBA-2015-0682.html