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

fix(koa-rest-api): Use per Gantry environment concurrency group in dev #165

Merged
merged 3 commits into from
Jul 27, 2020

Conversation

tobyhei
Copy link

@tobyhei tobyhei commented Jul 26, 2020

Matches the production concurrency group configuration.

@tobyhei tobyhei requested a review from a team as a code owner July 26, 2020 12:39
@changeset-bot
Copy link

changeset-bot bot commented Jul 26, 2020

🦋 Changeset is good to go

Latest commit: baba737

We got this.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@tobyhei
Copy link
Author

tobyhei commented Jul 26, 2020

I believe we should use this now Gantry uses it's own lock anyway we can't get around it.

Copy link
Contributor

@etaoins etaoins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The lock is released a couple of times during a deploy which allows limited concurrency and forward progress if you're lucky. On the other hand, using a concurrency group prevents wasting a whole Buildkite task on just spinning on the DynamoDB lock. It's easy to tie up 10 agents just waiting for locks if there's a lot of merges at once.

I think this is a net win and also aligns ourselves with prod.

@tobyhei tobyhei merged commit 1736ff8 into master Jul 27, 2020
@tobyhei tobyhei deleted the per-env-gantry-lock branch July 27, 2020 02:44
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

Successfully merging this pull request may close these issues.

None yet

3 participants