Closed GoogleCodeExporter closed 9 years ago
This would be easy to implement in mk-audit, but in some of the other scripts it
would be more difficult. In general, I think we'll need to come up with
policies for
each script which dictate how broken tables or other oddities should be handled.
Original comment by dan...@percona.com
on 8 Jan 2009 at 11:56
Original comment by baron.schwartz
on 3 May 2009 at 2:55
Summary was "mk-* die on tables marked as crashed"
Original comment by dan...@percona.com
on 5 Jun 2009 at 3:06
Original comment by baron.schwartz
on 7 Jun 2009 at 8:38
Given the impending retirement of mk-audit I'm closing this issue. The other
scripts
are pretty good about catching errors/dying gracefully. Do this has become
common
practice. I'm sure there is still un-eval-ed code lurking around, but as I
update,
fix, refactor, etc. things, I usually try to implement this practice of better
error
handling.
Original comment by dan...@percona.com
on 25 Nov 2009 at 9:36
Original issue reported on code.google.com by
ryan.a.l...@gmail.com
on 16 Nov 2008 at 3:10