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

Horizon needs Redis available to start #58

Open
holysoles opened this issue Jan 25, 2025 · 1 comment
Open

Horizon needs Redis available to start #58

holysoles opened this issue Jan 25, 2025 · 1 comment

Comments

@holysoles
Copy link
Contributor

Horizon requires Redis/Valkey being available to start properly. This can fail during initial deployment

[2025-01-25 05:51:24] production.ERROR: Connection refused [tcp://valkey-primary:6379] {"exception":"[object] (Predis\\Connection\\ConnectionException(code: 111): Connection refused [tcp://valkey-primary:6379] at /var/www/vendor/predis/predis/src/Connection/AbstractConnection.php:144)

When pixelfed is deployed in a single pod, this is problematic since Horizon exits, but the rest of the pod continues to run (I think this is because of the CMD script of the container?)

When pixelfed is deployed with a separate worker pod, this is less problematic, but the pod will restart a few times.

Not sure of the best solution right now, but figured I'd document this.

@jessebot
Copy link
Collaborator

Hmmm, we can separate the deployments and put a liveness/readiness probe on the horizon deployment to retry x amount of times. Maybe have it try 10 times to be safe? I feel like as long as it eventually becomes healthy, that's ok?

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