Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Worker Active Clients metric can exceed 0 at rest
See original GitHub issueAlluxio Version: What version of Alluxio are you using?
2.6.2
Describe the bug A clear and concise description of what the bug is.
When performing back-to-back bin/alluxio runTests, it is possible to see the Worker.ActiveClients metric exceed
0 while at rest (i.e: there are no active jobs). This implies that the metric counter is being incremented more than it is decremented, or that there are hanging jobs.
To Reproduce Steps to reproduce the behavior (as minimally and precisely as possible)
- Install an Alluxio cluster locally following the documentation.
- Perform a couple
bin/alluxio runTests. - Observe the
Worker.ActiveClientsmetric at a Alluxio worker metrics sink.
Expected behavior
The metric Worker.ActiveClients should be 0 when there are no jobs.
Additional context This metric was added as part of https://github.com/Alluxio/alluxio/pull/13856
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jiacheliu3 I also encountered this problem and submitted a PR https://github.com/Alluxio/alluxio/pull/14088 to solve this problem
fyi @dbw9580