Skip to content
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

Refactor: pengine: Reschedule specific monitors when resource definitions have changed #652

Merged
merged 2 commits into from
Mar 2, 2015

Conversation

gao-yan
Copy link
Member

@gao-yan gao-yan commented Feb 26, 2015

Resolved memory leaks. Well, and refactored -- I think it's more precise to reschedule specific monitors ;-)

@beekhof
Copy link
Member

beekhof commented Feb 26, 2015

I'm confused... doesn't this reverse the commits you had me merge yesterday?

@gao-yan
Copy link
Member Author

gao-yan commented Feb 27, 2015

Not actually. The idea of this commit is similar -- to record it in check_action_definition(), and only mark it as "required" in RecurringOp(). This one uses an optional monitor in check_action_definition(), utilizes the op flag instead of resource flag to record that -- I think it should be better to make that precise when it's possible.

@beekhof
Copy link
Member

beekhof commented Mar 2, 2015

Ah, I see now.

beekhof added a commit that referenced this pull request Mar 2, 2015
Refactor: pengine: Reschedule specific monitors when resource definitions have changed
@beekhof beekhof merged commit 6ef9d42 into ClusterLabs:master Mar 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants