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.
Subject
Views
Written By
Posted
1844
February 14, 2014 05:13PM
893
February 16, 2014 12:16AM
1367
February 16, 2014 09:07AM
866
February 17, 2014 11:44AM
1018
February 17, 2014 01:31PM
Re: Replication doesn't write to database.
960
February 20, 2014 12:44PM
970
February 26, 2014 12:21PM
882
February 26, 2014 03:33PM
798
February 27, 2014 08:20PM
819
February 28, 2014 11:07AM
879
March 03, 2014 04:35PM
930
March 05, 2014 10:15AM
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.