MySQL Forums
Forum List  »  InnoDB

Re: risk for innodb_flush_method=nosync
Posted by: Mike Hill
Date: May 31, 2019 01:13AM

It is the my.cnf. Is it OK?
I want to make sure if innodb_flush_method=nosync can disable fsync, reduce disk overhead by discarding the Druability.
Thanks a lot.

#----------------------------------------------------------------------
[mysqld]
character-set-server = utf8
explicit_defaults_for_timestamp = true
datadir = /home/data/mysql-5.6/data
tmpdir = /home/data/mysql-5.6/tmp
socket = /var/lib/mysql/mysql-5.6.sock
symbolic-links = 0
skip-name-resolve
sql_mode = NO_ENGINE_SUBSTITUTION

##Cache
thread_cache_size = 16
thread_concurrency = 16

table-open-cache = 4096
table-definition-cache = 2048

query-cache-size = 0

sort-buffer-size = 2M
join-buffer-size = 2M

## Temp Tables
tmp-table-size = 256M
max-heap-table-size = 256M

## Networking
back-log = 300
max-connections = 10000
max-connect-errors = 10000
max-allowed-packet = 32M
interactive-timeout = 3600
wait-timeout = 600


## Storage Engines
default-storage-engine = InnoDB
innodb = FORCE


## InnoDB
innodb-buffer-pool-size = 128G
innodb-log-file-size = 512M
innodb-log-buffer-size = 32M
innodb-file-per-table = 1
innodb-open-files = 3000
innodb_flush_log_at_trx_commit = 0
innodb_thread_concurrency = 16
innodb_lock_wait_timeout = 120
innodb_max_dirty_pages_pct = 90


skip-innodb-doublewrite
innodb_flush_method = nosync #IS IT OK?
#--------------------------------------------------------------------------------------------------------

## Replication
server-id = 4
skip-slave-start
log-bin = /home/data/mysql-5.6/binlogs/bin-log
log-bin-index = /home/data/mysql-5.6/binlogs/master-log-bin.index
log-error = /home/data/mysql-5.6/binlogs/master-error.log
relay-log = /home/data/mysql-5.6/binlogs/slave-relay.log
relay-log-info-file = /home/data/mysql-5.6/binlogs/slave-relay-log.info
relay-log-index = /home/data/mysql-5.6/binlogs/slave-relay-log.index
sync-binlog = 0
auto-increment-increment = 7
auto-increment-offset = 4
log-slave-updates
max-binlog-size = 1024M
binlog_cache_size = 1M
binlog_checksum = NONE
binlog_format = "MIXED"
expire-logs-days = 99


## Logging
log-output = FILE
slow-query-log = 1
slow-query-log-file = /home/data/mysql-5.6/logs/slow-log
log-slow-slave-statements
long-query-time = 2

[mysqld_safe]
log-error = /home/data/mysql-5.6/logs/mysqld.log
open-files-limit = 65535
[mysql]
no-auto-rehash
default-character-set = utf8
socket = /var/lib/mysql/mysql-5.6.sock
[mysqladmin]
socket = /var/lib/mysql/mysql-5.6.sock
[mysqldump]
socket = /var/lib/mysql/mysql-5.6.sock

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: risk for innodb_flush_method=nosync
79
May 31, 2019 01:13AM


Sorry, only registered users may post in this forum.

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.