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

Explicitly WARN about pausing/throttling and binlog expiration #57

Closed
rlowe opened this issue Jun 7, 2016 · 1 comment
Closed

Explicitly WARN about pausing/throttling and binlog expiration #57

rlowe opened this issue Jun 7, 2016 · 1 comment

Comments

@rlowe
Copy link

rlowe commented Jun 7, 2016

<captaineyesight>Might I suggest putting some kind of bolded note about only being able to throttle as long as binary logs hang around. I know it should be 100% obvious for everything else written. I just don’t want someone crying that they paused their schema change for 10 days and they only saved 5 days of binary logs and that somehow is the tools fault.

<rlowe> I'd go one step further and warn interactively when they pause where possible.`
@shlomi-noach
Copy link
Contributor

Closed by #112

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

No branches or pull requests

2 participants