Skip to content

Conversation

@wodCZ
Copy link
Contributor

@wodCZ wodCZ commented Jun 25, 2021

The 2s interval caused constantly high CPU usage. 30s interval with 3 retries is the Docker default and doesn't hurt the system that much.
Fixes #1000

The 2s interval caused constantly high CPU usage. 30s interval with 3 retries is the Docker default and doesn't hurt the system that much.
Fixes getsentry#1000
Copy link
Member

@BYK BYK left a comment

Choose a reason for hiding this comment

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

Looks good to me, thanks a lot!

A few requests tho:

  1. Since these are all the same now, would you mind grouping out them like we do with *restart_policy?
  2. From #1000, would you mind adding references to those known moby issues into the code for future reference?

@wodCZ
Copy link
Contributor Author

wodCZ commented Jun 25, 2021

Great ideas, thank you. Updated 👌

Copy link
Member

@BYK BYK left a comment

Choose a reason for hiding this comment

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

Thanks a lot! 🚀

@BYK BYK enabled auto-merge (squash) June 28, 2021 09:48
@BYK BYK merged commit e25e36b into getsentry:master Jun 28, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

High CPU usage after update

2 participants