-
Notifications
You must be signed in to change notification settings - Fork 9
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
Default redis DB numbers to 0 and 1 TASK-790 #73
base: main
Are you sure you want to change the base?
Default redis DB numbers to 0 and 1 TASK-790 #73
Conversation
# - KPI Broker - 1 | ||
# - Kobocat Broker - 1 | ||
# - KPI Cache - 1 | ||
# - Service account - 1 |
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.
For the record: Going to be gone soon
@@ -91,8 +91,8 @@ kpi: | |||
secret: | |||
{} | |||
# DATABASE_URL: "postgres://postgres:password@postgres-postgresql:5432/postgres" | |||
# CELERY_BROKER_URL: "redis://localhost:6379/2" | |||
# CACHE_URL: "redis://localhost:6379/4" | |||
# CELERY_BROKER_URL: "redis://localhost:6379/1" |
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.
Could this create zombie tasks? (e.g. workers and broker not speaking to each other until the deployment is totally done?)
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.
Just one question. Otherwise LGTM
Consolidate redis DB numbers to just 0 and 1. Simplifies configuration and gets us closer to supporting redis cluster. Since we aren't changing enketo nor sessions - this change should be safe to make without any data migration.