search

hugowan / maatkit

Automatically exported from code.google.com/p/maatkit
0 stars 0 forks source link

Scripts should die or do something useful on tables marked as crashed #129

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
%> perl mk-audit
...
                default=8192_87380_174760
        - Not default value /proc/sys/net/ipv4/tcp_wmem:
                set=4096_16384_4194304
                default=4096_16384_131072
DBD::mysql::db selectrow_hashref failed: Table './XXX/YYY' is marked as
crashed and should be repaired at mk-audit line 159.
Issuing rollback() for database handle being DESTROY'd without explicit
disconnect().
[guest@bonnie bin]$ 

Any way it can simply acknowledge the crashed table and continue gracefully?

[guest@bonnie bin]$ uname -a
Linux bonnie 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
[guest@bonnie bin]$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 5.1 (Tikanga)
[guest@bonnie bin]$ mysql -ss
mysql> select @@version;
5.0.22-log

Original issue reported on code.google.com by ryan.a.l...@gmail.com on 16 Nov 2008 at 3:10

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago

Original comment by baron.schwartz on 3 May 2009 at 2:55

GoogleCodeExporter commented 9 years ago 
Summary was "mk-* die on tables marked as crashed"

Original comment by dan...@percona.com on 5 Jun 2009 at 3:06

GoogleCodeExporter commented 9 years ago

Original comment by baron.schwartz on 7 Jun 2009 at 8:38

GoogleCodeExporter commented 9 years ago 
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