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

🚀| Change active containers from in-ram table to a database #51

Open
byawitz opened this issue Feb 14, 2024 · 2 comments
Open

🚀| Change active containers from in-ram table to a database #51

byawitz opened this issue Feb 14, 2024 · 2 comments

Comments

@byawitz
Copy link
Contributor

byawitz commented Feb 14, 2024

Currently, scaling the executor is challenging because the activeRuntimes variable relies on a Swoole Table, rendering the executor container stateful.

The optimal solution would be to switch to a database, preferably Redis, to ensure the container is entirely stateless.

@eldadfux
Copy link
Member

This is actually designed this way because each executor is designed like an agent to orchestrate a single node. To scale it you would need to have a 2nd machine and load balance the two.

@eldadfux
Copy link
Member

That said, we could consider it for future development.

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

2 participants