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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Support pending tasks number metrics for Netty EventLoopGroup #1686

Closed
3 tasks done
rickyma opened this issue May 9, 2024 · 0 comments
Closed
3 tasks done

[FEATURE] Support pending tasks number metrics for Netty EventLoopGroup #1686

rickyma opened this issue May 9, 2024 · 0 comments

Comments

@rickyma
Copy link
Contributor

rickyma commented May 9, 2024

Code of Conduct

Search before asking

  • I have searched in the issues and found no similar issues.

Describe the feature

Through the metrics, we can know whether the current Netty Server has reached a performance bottleneck, whether tasks are accumulating, and thus be able to adjust the thread number of the Netty EventLoopGroup more accurately.

Motivation

No response

Describe the solution

No response

Additional context

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
rickyma added a commit to rickyma/incubator-uniffle that referenced this issue May 9, 2024
@rickyma
[apache#1686] feat(netty): Support pending tasks number metrics for N…
a057f2e 
…etty EventLoopGroup
@rickyma rickyma mentioned this issue May 9, 2024
Merged
rickyma added a commit to rickyma/incubator-uniffle that referenced this issue May 9, 2024
@rickyma
[apache#1686] feat(netty): Support pending tasks number metrics for N…
c11dee7 
…etty EventLoopGroup
jerqi pushed a commit that referenced this issue May 11, 2024
@rickyma
[#1686] feat(netty): Support pending tasks number metrics for Netty E…
7b63177 
…ventLoopGroup (#1687)

### What changes were proposed in this pull request?

Support pending tasks number metrics for Netty EventLoopGroup.

### Why are the changes needed?

For #1686.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Existing tests.
@rickyma rickyma closed this as completed May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rickyma