cryostatio / cryostatio/cryostat-agent
[Request] Shut down Agent without exiting host JVM
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 12
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 15
Description
Related #233
It should be possible to shut down the Agent cleanly without exiting the host JVM. This could be useful in one-off troubleshooting cases where the Agent functionality is only desired for a relatively short period of time, or in case the Agent causes some disruption to the host application JVM.
The first most obvious way to do this would be to use the existing SignalHandler to catch some user-configurable signal that the OpenJDK JVM does not already respond to by default. It could also be done by an authenticated WebServer request. In any case, the event should initiate an orderly shutdown of the Agent's webserver, harvester, and any other threads.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing SignalHandler and the Agent's webserver and harvester lifecycle code. Compare the signal and authenticated WebServer request approaches described in the issue, then trace how other Agent threads are started and stopped. Done means an orderly Agent shutdown that stops the webserver, harvester, and other Agent threads without exiting the host JVM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100