-
Notifications
You must be signed in to change notification settings - Fork 91
fix(deployment): Use unique Celery node names per worker replica. #2269
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -87,7 +87,7 @@ spec: | |||||
| "--concurrency", "{{ .Values.workerConcurrency }}", | ||||||
| "--loglevel", "WARNING", | ||||||
| "-Q", "compression", | ||||||
| "-n", "compression-worker" | ||||||
| "-n", "compression-worker@%h" | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @gibber9809 and i discussed offline - let's update https://github.com/y-scope/clp/blob/aeb077ca4/tools/deployment/package/docker-compose-all.yaml#L329 to match this command argument though, practically, that fix won't be enough to ensure uniqueness in the docker compose services:
since satisfying 2 + 3 will involve changing a lot of code, i think simply aligning the command in
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. that said, as pointed out by @gibber9809 , the above proposal will only ensure uniqueness across different compression-worker replicas on the same host where the docker-compose project runs. (which is still valuable as we can debug multi worker issues without a multi host cluster) however, if the docker compose project is run across multiple hosts to form a cluster, hostnames can still collide. as proposed by #2274 , maybe we should formally remove mulithost support in the docker compose flow |
||||||
| ] | ||||||
| volumes: | ||||||
| - name: {{ include "clp.volumeName" (dict | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -87,7 +87,7 @@ spec: | |
| "--concurrency", "{{ .Values.workerConcurrency }}", | ||
| "--loglevel", "WARNING", | ||
| "-Q", "query", | ||
| "-n", "query-worker" | ||
| "-n", "query-worker@%h" | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ditto - let's update https://github.com/y-scope/clp/blob/aeb077ca4/tools/deployment/package/docker-compose-all.yaml#L516 to match this command argument |
||
| ] | ||
| volumes: | ||
| - name: {{ include "clp.volumeName" (dict | ||
|
|
||
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.
the git branch's base seems to be out of date. please merge origin (y-scope)'s
mainbranch into the PR source branch