PW Pool: Reduce task-to-task corruption risk #199
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously instances would shutdown and auto-terminate if the controlling VM's `SetupInstances.sh` examined the remote worker log and found >= `PW_MAX_TASKS` logged. However after examining the production `Cron.log`, it was found that nowhere near this number of tasks is actually running during `PW_MAX_HOURS`. Cut the value in half to lower the risk of one/more tasks corrupting processes or the filesystem for other tasks. Note: Eyeball average tasks before timed auto-shutdown was about 7 Signed-off-by: Chris Evich <[email protected]>
|
The cirrus-ci/build-push_test error |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously instances would shutdown and auto-terminate if the controlling VM's
SetupInstances.shexamined the remote worker log and found >=PW_MAX_TASKSlogged. However after examining the productionCron.log, it was found that nowhere near this number of tasks is actually running duringPW_MAX_HOURS. Cut the value in half to lower the risk of one/more tasks corrupting processes or the filesystem for other tasks.Note: Eyeball average tasks before timed auto-shutdown was about 7