-
Notifications
You must be signed in to change notification settings - Fork 243
Refactor for a single horizon instance to improve memory #8565
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
Conversation
gusys
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me...
|
QA server K8S was successfully deployed https://tenant-1.ci-0e973e832f.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://tenant-1.ci-0e973e832f.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://tenant-1.ci-0e973e832f.engk8s.processmaker.net |
|
|
QA server K8S was successfully deployed https://tenant-1.ci-0e973e832f.engk8s.processmaker.net |





Instead of running
TENANT=X php artisan horizonfor each tenant, we need a single instance of horizon to handle all tenants due to memory consumption. Every instance of horizon uses the full application memory in a long running process so the pod was running out of memory and crashing.This refactor allows the jobs to bootstrap a fresh application instance using the tenant id saved in the job context.
We have to bootstrap a fresh application each time because the long-running horizon job always shares the same application in memory.
ci:deploy
ci:multitenancy
ci:k8s-branch:multitenancy
..