Immutable solution version
Updating worker concurrency doesn't reflect in the response or UI
Complete solution
Covers this Astronomer problem: Updating worker concurrency doesn't reflect in the response or UI. This was fixed in a later astro-cli release.
The problem
Issue astronomer/astro-cli#1267 (closed, 8 comments): While attempting to update the worker-queue's concurrency through ``astro deployment worker-queue update command, using the flag --concurrency int to alter the concurrency of a given astro machine doesn't change the concurrency value for the updated worker queue. However, the astromachine gets updated successfully. `` shrividyahegde@Shrividyas-MacBook-Pro Documents % astro deployment worker-queue update --concurrency 30 Select a Deployment # DEPLOYMENT NAME RELEASE NAME DEPLOYMENT ID DAG DEPLOY ENABLED 1 gcpteststandard planetoidal-gegenschein-1614 clix117rh103281jxa9sgyorxg...
What fixed it
This was fixed in a later astro-cli release. Update the CLI and the astro deployment worker-queue update --concurrency N command works again. Concurrency is validated against the worker type, so keep the value inside the allowed range for your machine: A5 takes 1-15, A10 1-30, A20 1-60, A25 1-120. Zero or out-of-range values are rejected with an error that tells you the valid range.
Evidence
In gh:astronomer/astro-cli#1267 (Astronomer), the issue reported was: Issue astronomer/astro-cli#1267 (closed, 8 comments): While attempting to update the worker-queue's concurrency through ``astro deployment worker-queue update command, using the flag --concurrency int to alter the concurrency of a given astro machine doesn't change the concurrency value for the updated worker queue. However, the astromachine gets updated successfully. `` shrividyahegde@Shrividyas-MacBook-Pro Documents % astro deployment worker-queue update --concurrency 30 Select a Deployment # DEPLOYMENT NAME RELEASE NAME DEPLOYMENT ID DAG DEPLOY ENABLED 1 gcpteststandard planetoidal-gegenschein-1614 clix117rh103281jxa9sgyorxg... The verified resolution from the thread: This was fixed in a later astro-cli release. Update the CLI and the astro deployment worker-queue update --concurrency N command works again. Concurrency is validated against the worker type, so keep the value inside the allowed range for your machine: A5 takes 1-15, A10 1-30, A20 1-60, A25 1-120. Zero or out-of-range values are rejected with an error that tells you the valid range. Source: mount the host path https at container path //github.com/astronomer/astro-cli/issues/1267
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_SjR0ceFDkQ410LOM-gaKgg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Updating worker concurrency doesn't reflect in the response or UI <span>— Vectle</span></a>