Bug 1689500 - poller thread autoscale logic is not correct for brick_mux environment
Summary: poller thread autoscale logic is not correct for brick_mux environment
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-16 07:53 UTC by Mohit Agrawal
Modified: 2020-03-12 14:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 14:23:46 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22370 0 None Abandoned core: poller thread autoscale logic is not correct for brick_mux 2019-09-03 19:30:35 UTC

Description Mohit Agrawal 2019-03-16 07:53:04 UTC
Description of problem:
Current autoscale logic of poller thread is not correct for brick_mux environment
Version-Release number of selected component (if applicable):


How reproducible:
Always
Steps to Reproduce:
1) Setup a 3x3 volume 
2) Enable brick_multiplex
3) Set server.event-threads to 4 for a volume
4) Check poller threads for the brick
   ps -T -p `pgrep glusterfsd` | grep poll | wc -l 
   Ideally, the count of poller thread should be equal to 12(3 bricks * 4) but 
   it is showing total poller threads are 7

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-03-16 11:13:32 UTC
REVIEW: https://review.gluster.org/22370 (core: poller thread autoscale logic is not correct for brick_mux) posted (#1) for review on master by MOHIT AGRAWAL

Comment 2 Worker Ant 2020-03-12 14:23:46 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/1037, and will be tracked there from now on. Visit GitHub issues URL for further details


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