Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug:1689500] poller thread autoscale logic is not correct for brick_mux environment #1037

Closed
gluster-ant opened this issue Mar 12, 2020 · 3 comments
Assignees
Labels
Migrated Type:Bug wontfix Managed by stale[bot]

Comments

@gluster-ant
Copy link
Collaborator

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:

  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:

@gluster-ant
Copy link
Collaborator Author

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

@stale
Copy link

stale bot commented Oct 8, 2020

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.

@stale stale bot added the wontfix Managed by stale[bot] label Oct 8, 2020
@stale
Copy link

stale bot commented Oct 23, 2020

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.

@stale stale bot closed this as completed Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Migrated Type:Bug wontfix Managed by stale[bot]
Projects
None yet
Development

No branches or pull requests

2 participants