Mysql configuration innodb_flush_method parameter problem-CodePudding

Version is 5.7.12
In my. Ini innodb_flush_method why this parameter regardless of the setting value, can't start the mysql, only the parameters are commented out to start the service, [ERROR] InnoDB: Unrecognized value O_DSYNC for innodb_flush_method this is how to return a responsibility?
But not set parameters, the database will not be able to manipulate data, log, for example:
The 2017-05-04 T15: shall. 695625 + 08:00 0 [ERROR] InnoDB: Unrecognized value fdatasync for innodb_flush_method

CodePudding user response:

Your system is Windows, Linux,

Try set to this value: fdatasync

CodePudding user response:

reference 1st floor yupeigu response:

your system is Windows, Linux,

Try to set to this value: fdatasync

Windows 7 can three values are tried, just add this parameter, it is the error... uncomfortable

CodePudding user response:

According to the official website of the document that your mistake is O_DSYNC information display, but you said you is Windows 7, it is clearly in the wrong bai
Permitted Values (Unix) Type string
NULL
O_DSYNC
Littlesync
Nosync
O_DIRECT
O_DIRECT_NO_FSYNC

Permitted Values (Windows) in the Type string
NULL
Normal
Unbuffered

CodePudding user response:

Win10 test under the two are no problem, NULL is not specified, tried to be specified in the configuration file NULL
Innodb_flush_method=normal
Innodb_flush_method=unbuffered

CodePudding user response:

refer to the second floor A771690440 response:

Quote: refer to 1st floor yupeigu response:

Your system is Windows, Linux,

Try to set to this value: fdatasync

Windows 7 can three values are tried, just add this parameter, it is the error... Sad

, at startup, mysql does not need to specify this parameter, you can start

CodePudding user response:

reference ZJCXC reply: 3/f

according to the official website of the document that your error message display with the O_DSYNC, but you said you is Windows 7, it is clearly in the wrong bai
Permitted Values (Unix) Type string
NULL
O_DSYNC
Littlesync
Nosync
O_DIRECT
O_DIRECT_NO_FSYNC

Permitted Values (Windows) in the Type string
NULL
Normal
Unbuffered

CodePudding user response:

Power under the Windows are always bad library, which should be selected

CodePudding user response:

Under the Windows mysql5.6.20 power always have bad library, how to optimize configuration is better

CodePudding user response:

refer to 7th floor l270378034 response:

power under the Windows are always bad library, should choose which

My configuration is as follows

 log - bin.=my bin 
Binlog_format=mixed 
Server - id=1 

Max_connect_errors=3000 
Wait_timeout=2880000 
Interactive_timeout=2880000 
# close buffer 
Query_cache_size=0 
Query_cache_type=0 
# int type can be null 
SQL - mode=NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 

Max_allowed_packet=256 MB 
Read_buffer_size=8 m 
Read_rnd_buffer_size=16 m 
Lower_case_table_names=1 
Key_buffer_size=15 m 

Table_open_cache=400 
Table_definition_cache=400 
Table_open_cache_instances=64 
Metadata_locks_hash_instances=64 

Sort_buffer_size=16 m 
Join_buffer_size=16 m 
Thread_cache_size=768 
Query_cache_size=0 
Query_cache_type=0 
Both tmp_table_size=96 m 
Performance_schema=OFF 
Open_files_limit=65535 
Back_log=1024 

Innodb_buffer_pool_size=512 MB 
Innodb_buffer_pool_instances=8 
Innodb_buffer_pool_load_at_startup=1 
Innodb_buffer_pool_dump_at_shutdown=1 
Innodb_io_capacity=4000 
Innodb_io_capacity_max=8000 
Innodb_flush_neighbors=0 
Innodb_write_io_threads=8 
Innodb_read_io_threads=8 
Innodb_purge_threads=4 
# not start innodb_page_cleaners=4 
# ib_logfile0 or 1 size 
Innodb_log_file_size=512 MB 
# 4 MB - 8 MB ok 
Innodb_log_buffer_size=32 m 
Innodb_flush_log_at_trx_commit=1 
Innodb_file_per_table=1 
External - locking=FALSE 
# the skip - external - locking 
Expire_logs_days=90 
Max_binlog_size=500 m 
Skip - name - resolve=OFF