Skip to content
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.

SDI-818: Restart failed plugins #688

Merged
merged 6 commits into from
Feb 18, 2016
Merged

Conversation

candysmurf
Copy link
Contributor

resolves #497.

@tiffanyfay
Copy link
Contributor

You need to rebase.

@jcooklin jcooklin force-pushed the sdi-818-jc branch 2 times, most recently from 076db64 to 6a11381 Compare February 2, 2016 05:03
@candysmurf candysmurf force-pushed the sdi-818-jc branch 4 times, most recently from 3f7c3f0 to 697339b Compare February 2, 2016 22:44
@jcooklin jcooklin force-pushed the sdi-818-jc branch 3 times, most recently from a20eaa4 to 8359a3b Compare February 3, 2016 01:36

if pool.Eligible() {
if pool.RestartCount() < MaxPluginRestartCount {
e := r.restartPlugin(v.Key)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's add a log statement (warn) that we restarted plugin (name:version) x times.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Add the warn log. please check. thanks

@jcooklin
Copy link
Collaborator

LGTM, after adding warn statement when restarting and rebasing.

jcooklin added a commit that referenced this pull request Feb 18, 2016
SDI-818: Restart failed plugins
@jcooklin jcooklin merged commit be26613 into intelsdi-x:master Feb 18, 2016
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.

A failed or panicked available plugin can leave an apPool with not enough resources.
3 participants