Skip to content

/ saltfs

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

Jump to bottom

Handle buildbot-master OOMs better #406

Closed
aneeshusa opened this issue Jun 26, 2016 · 3 comments
Closed

Handle buildbot-master OOMs better #406

aneeshusa opened this issue Jun 26, 2016 · 3 comments

Comments

@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Jun 26, 2016

I just noticed that Buildbot was down and looking at the logs it seems the buildbot-master process was OOM killed. I've gone ahead and restarted it for now so that it is back up. If this starts happening repeatedly, we may want to give servo-master1 more memory.
@aneeshusa
Copy link
Member Author

@aneeshusa aneeshusa commented Jun 27, 2016 •
edited

I just saw that this happened again, seems like it may not just be an intermittent problem.
@aneeshusa
Copy link
Member Author

@aneeshusa aneeshusa commented Jun 27, 2016

servo-master1 now has 7.5 GB of memory (up from 3.75 GB).
@aneeshusa aneeshusa closed this Jun 27, 2016
@larsbergstrom
Copy link
Contributor

@larsbergstrom larsbergstrom commented Jun 27, 2016

Yes, I moved this to a m3.large instance. It looks like the buildbot instance itself was ballooning up to > 1GB of memory usage on some very large PRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@larsbergstrom @aneeshusa
You can’t perform that action at this time.