Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1689500

Summary:	poller thread autoscale logic is not correct for brick_mux environment
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, pasik
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 14:23:46 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 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