Timeline for MySQL Tables crashing randomly
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2013 at 0:07 | vote | accept | Tiffany Walker | ||
| Feb 5, 2013 at 15:06 | comment | added | mdoyle | Corruption can cause mysqld to crash, which can cause further corruption, so yes. It is theoretically possible for a bug in the data storage code that results in certain queries causing a crash, per the MySQL troubleshooting docs. | |
| Feb 4, 2013 at 19:49 | comment | added | Tiffany Walker | So corrupted tables can cause other tables to crash? -- Is it really possible for a query to crash MySQL or a Table? | |
| Feb 4, 2013 at 16:49 | comment | added | mdoyle | It's hard to say from the info given. Crashes can cause corruption, and corruption can cause crashes. All we have is evidence of one crash. It is not likely that it is a bug, but it is possible. If you follow the steps above to try to isolate a query that is causing a crash, and you can replicate that crash reliably, it's almost certainly a bug and should be submitted. | |
| Feb 4, 2013 at 16:28 | comment | added | Tiffany Walker | Thanks for the info. Did not know you could run more then one instance of mysqld. So this could just be a bugged version of MySQL? | |
| Feb 4, 2013 at 14:26 | comment | added | mdoyle | It may be that I am being overly cautious, but in the event that you somehow have an actual bug in your version of mysqld, I would try to bypass it in verifying that your tables are starting up uncorrupted by cutting it out. Since mysqlcheck is basically just an interface to mysqld, invoking mysqlcheck would also potentially be invoking the bug. It's not very likely, but it is a possibility. | |
| Feb 4, 2013 at 14:22 | comment | added | mdoyle | A single instance can have multiple threads, which is what I assume htop is showing you. If top shows only one mysqld running, you have only one instance running. | |
| Feb 3, 2013 at 2:27 | comment | added | Tiffany Walker | top shows 1 mysqld running and htop shows more. So htop is showing the threads right? So that would mean its more then one instance? -- alright so in other words you use mysqlcheck if mysqld is running and myisamchk if its not running? | |
| Feb 2, 2013 at 14:17 | comment | added | mdoyle | By multiple instances I mean more than one mysqld process running concurrently. The biggest difference between mysqlcheck and myisamchk is that mysqlcheck is a client application that sends requests through the MySQL server, so it requires mysqld to be running in order to function. myisamchk is a utility that operates directly on the files--it's best if mysqld is NOT running. If you use myisamchk, you can verify integrity before starting mysqld--I thought that might eliminate one more variable in the troubleshooting process. | |
| Feb 1, 2013 at 21:57 | comment | added | Tiffany Walker | What do you mean by multiple instances? The datacenter confirmed it is not a bad drive issue. So they are doing a RAM test with mcelog. How is myisamchk different from mysqlcheck that I commonly use? | |
| Feb 1, 2013 at 20:53 | history | answered | mdoyle | CC BY-SA 3.0 |