You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Setup a 3x3 volume
Enable brick_multiplex
Set server.event-threads to 4 for a volume
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:
The text was updated successfully, but these errors were encountered:
Time: 20190316T11:13:32
bugzilla-bot at gluster.org commented:
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
Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.
URL: https://bugzilla.redhat.com/1689500
Creator: moagrawa at redhat
Time: 20190316T07:53:04
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:
ps -T -p
pgrep glusterfsd
| grep poll | wc -lIdeally, 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:
The text was updated successfully, but these errors were encountered: