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

Thread usage is opaque, add monitor on dispatch thread and tooling to understand it #40

Open
daviddawson opened this issue Feb 6, 2017 · 1 comment

Comments

@daviddawson
Copy link
Member

Muon Version: 7.1.6
Language: JVM

As seen in muoncore/photon#5 it is possible for protocols to be written that do excessive wsork (even block) the main dispatch thread. This will either slow event dispatch, or cause it to stop completely, killing the muon service.

This behaviour should be monitored and alerted if possible. Other worker pools should also be monitored and metrics provided.

@daviddawson
Copy link
Member Author

Centralised thread usage in 078a189

Now needs the ring dispatch to be monitored and the pool to be managed to fully fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant