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

Optionally throttle based on the lag of a single slave #14

Merged
merged 2 commits into from
Nov 22, 2016

Conversation

baldowl
Copy link
Member

@baldowl baldowl commented Oct 7, 2016

New option :check_only expects a lambda returning a connection config fragment for the specific slave; however, beware that credentials for the master are use to connect to this slave.

R: @sroysen, @jordanwheeler.

New option `:check_only` expects a lambda returning a
connection config fragment for the specific slave; however,
beware that credentials for the master are use to connect
to this slave.
@sroysen
Copy link

sroysen commented Nov 1, 2016

@jasonhl , can you take a look at this?

end
else
slave_config = @check_only.call
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it worth adding a check (and a corresponding test...) here in case the parameter passed in is not something that responds to "call"?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, I think it makes sense. I'll add it.

@jasonhl
Copy link
Collaborator

jasonhl commented Nov 2, 2016

Looks good. Just one question/comment.

@baldowl
Copy link
Member Author

baldowl commented Nov 22, 2016

@jasonhl: I've just added that check.

@baldowl baldowl merged commit 6619b8f into master Nov 22, 2016
@baldowl baldowl deleted the cherry-pick-a-single-slave branch November 22, 2016 13:40
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.

3 participants