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

Store status update reason field in SingularityTaskHistoryUpdate #900

Merged
merged 4 commits into from Feb 22, 2016

Conversation

Projects
None yet
1 participant
@tpetr
Member

tpetr commented Feb 17, 2016

This will allow us to determine whether or not a task was killed due to a mesos OOM kill. Also sets statusMessage to Task exceeded memory limit of XXX MB if no message was set in the status update from Mesos.

@tpetr tpetr added the hs_staging label Feb 17, 2016

@tpetr tpetr added this to the 0.4.10 milestone Feb 17, 2016

@tpetr tpetr added the hs_qa label Feb 17, 2016

@tpetr tpetr added the hs_stable label Feb 17, 2016

@tpetr tpetr modified the milestones: 0.4.10, 0.4.11 Feb 18, 2016

tpetr added a commit that referenced this pull request Feb 22, 2016

Merge pull request #900 from HubSpot/mesos-oom
Store status update reason field in SingularityTaskHistoryUpdate

@tpetr tpetr merged commit 3ed3eb1 into master Feb 22, 2016

1 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build failed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@tpetr tpetr deleted the mesos-oom branch Feb 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment