MySQL Forums
Forum List  »  Replication

Re: Replication doesn't write to database.
Posted by: Rick James
Date: February 20, 2014 12:44PM

> key_buffer_size = 3276M

Wasting RAM if your tables are all InnoDB. Recommend 50M.

> query_cache_size = 3276M

Likely to cause slowdowns (and waste RAM). Use no more than 50M.

> table_cache = 2000

Do you have 2000 tables? Suggest 200.

> tmp_table_size= 3276M
> max_heap_table_size = 3276M

How much RAM do you have? Suggest no more than 64M unless you have a huge RAM and/or large MEMORY tables.

> | innodb_data_home_dir | |

This setting feels wrong, but I don't know what it should be in your case.

Recommend you create a directory on your SSD, and put mysql's data dir in it, not at the top level. That would at least avoid the .lost+found hiccup.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Replication doesn't write to database.
957
February 20, 2014 12:44PM


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.