remove contract specification from SMF manifests (solaris)#63
Merged
jaredmorrow merged 1 commit intobasho:masterfrom Jun 21, 2013
Merged
Conversation
SMF uses the property, that this commit removes to determine how the service should be affected under failure conditions. This commit makes it so SMF reverts to its default behavior to consider a service as "failed" if *any* of the processes that make up the service dump core, or if *any* of the processes receive a fatal signal originating outside of the service (ie. if a processes raises its own signal or sends a signal to another process within the same service that doesn't cause a core dump, SMF ignores it) It is in my experience running Riak in production at Voxer, if a core dump is generated, the service will think riak is alive and healthy, even though it is completely unresponsive. This change makes it so any fatal signal to any of the processes controlled by SMF for riak will trigger SMF to restart the service, as well as if any of the processes dump core
Contributor
|
+1, thanks @bahamas10 |
jaredmorrow
added a commit
that referenced
this pull request
Jun 21, 2013
remove contract specification from SMF manifests (solaris)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
SMF uses the property (ignore_error), that this commit removes to determine how
the service should be affected under failure conditions.
This commit makes it so SMF reverts to its default behavior
to consider a service as "failed" if any of the processes
that make up the service dump core, or if any of the processes
receive a fatal signal originating outside of the service (ie.
if a processes raises its own signal or sends a signal to another
process within the same service that doesn't cause a
core dump, SMF ignores it)
It is in my experience running Riak in production at Voxer, if
a core dump is generated, the service will think riak is alive and
healthy, even though it is completely unresponsive.
This change makes it so any fatal signal to any of the processes
controlled by SMF for riak will trigger SMF to restart the service,
as well as if any of the processes dump core