MySQL Forums
Forum List  »  General

Re: Finding the cause of a crashed table
Posted by: MC Potgieter
Date: February 11, 2015 03:53AM

I've applied the parameters you've proposed. Will soon give you the results.
I ran into a couple of problems though.

After changing from MyISAM to InnoDB I cant access my trafficlog table.
The table is currently 1.5GB and can't read from it in my code or a query in MySQL Workbench.

It seems like I'm able to write to it but have'nt confirmed that.
Not sure what is the cause. How can I resolve this? Is there some way to check why I can't read from the table?

Also after changing innodb_buffer_pool_size = 1000M, I could not acces the database from root.

2015-02-11 11:05:02 6180 [ERROR] Error log throttle: 414 'Can't create thread to handle new connection' error(s) suppressed
2015-02-11 11:05:02 6180 [ERROR] Can't create thread to handle request (errno= 12)

I've reduced the value after which I could access the DB again.

After applying your propsed parameters, MySQL would not start.
I found the problem with the slow query log. This is what I've changed:

wait_timeout = 300
long_query_time = 10
slow_query_log_file = slow_query.log

After removing this, MySQL worked fine.

Options: ReplyQuote


Subject
Written By
Posted
Re: Finding the cause of a crashed table
February 11, 2015 03:53AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.