Async::Container::Supervisor
Provides a supervisor service for
Features
- Supports multi-process, multi-thread and hybrid containers.
- Automatic scalability based on physical hardware.
- Direct integration with systemd using
$NOTIFY_SOCKET
. - Internal process readiness protocol for handling state changes.
- Automatic restart of failed processes.
Usage
Please browse the source code index or refer to the guides below.
Getting Started
This guide explains how to get started with async-container-supervisor
to supervise and monitor worker processes in your Ruby applications.
Releases
Please browse the releases for more details.
v0.7.0
- If a memory leak is detected, sample memory usage for 60 seconds before exiting.
v0.6.4
- Make client task (in supervised worker) transient, so that it doesn't keep the reactor alive unnecessarily. It also won't be stopped by default when SIGINT is received, so that the worker will remain connected to the supervisor until the worker is completely terminated.
v0.6.3
- Add agent context documentation.
v0.6.2
- Fix timed out RPCs and subsequent responses which should be ignored.
v0.6.0
- Add
async:container:supervisor:reload
command to restart the container (blue/green deployment).
v0.1.0
- Initial implementation.
Contributing
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature
). - Commit your changes (
git commit -am 'Add some feature'
). - Push to the branch (
git push origin my-new-feature
). - Create new Pull Request.
Developer Certificate of Origin
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
Community Guidelines
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.