Pastebin launched a little side project called HostCabi.net, check it out ;-)Don't like ads? PRO users don't see any ads ;-)
Guest

20120814_galera1_my.cnf

By: lolomin on Aug 14th, 2012  |  syntax: None  |  size: 22.93 KB  |  hits: 80  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. #BEGIN CONFIG INFO
  2. #DESCR: 4GB RAM, InnoDB only, ACID, few connections, heavy queries
  3. #TYPE: SYSTEM
  4. #END CONFIG INFO
  5.  
  6. #
  7. # This is a MySQL example config file for systems with 4GB of memory
  8. # running mostly MySQL using InnoDB only tables and performing complex
  9. # queries with few connections.
  10. #
  11. # MySQL programs look for option files in a set of
  12. # locations which depend on the deployment platform.
  13. # You can copy this option file to one of those
  14. # locations. For information about these locations, see:
  15. # http://dev.mysql.com/doc/mysql/en/option-files.html
  16. #
  17. # In this file, you can use all long options that a program supports.
  18. # If you want to know which options a program supports, run the program
  19. # with the "--help" option.
  20. #
  21. # More detailed information about the individual options can also be
  22. # found in the manual.
  23. #
  24.  
  25. #
  26. # The following options will be read by MySQL client applications.
  27. # Note that only client applications shipped by MySQL are guaranteed
  28. # to read this section. If you want your own MySQL client program to
  29. # honor these values, you need to specify it as an option during the
  30. # MySQL client library initialization.
  31. #
  32. [client]
  33. #password       = [your_password]
  34. port            = 3306
  35. socket          = /var/run/mysqld/mysqld.sock
  36.  
  37. # *** Application-specific options follow here ***
  38.  
  39. #
  40. # The MySQL server
  41. #
  42. [mysqld]
  43.  
  44. # generic configuration options
  45. port            = 3306
  46. socket          = /var/run/mysqld/mysqld.sock
  47. #bind-address   = 192.168.0.49
  48. datadir         = /var/lib/mysql
  49.  
  50.  
  51. # back_log is the number of connections the operating system can keep in
  52. # the listen queue, before the MySQL connection manager thread has
  53. # processed them. If you have a very high connection rate and experience
  54. # "connection refused" errors, you might need to increase this value.
  55. # Check your OS documentation for the maximum value of this parameter.
  56. # Attempting to set back_log higher than your operating system limit
  57. # will have no effect.
  58. #back_log = 50
  59.  
  60. # Don't listen on a TCP/IP port at all. This can be a security
  61. # enhancement, if all processes that need to connect to mysqld run
  62. # on the same host.  All interaction with mysqld must be made via Unix
  63. # sockets or named pipes.
  64. # Note that using this option without enabling named pipes on Windows
  65. # (via the "enable-named-pipe" option) will render mysqld useless!
  66. #skip-networking
  67.  
  68. # The maximum amount of concurrent sessions the MySQL server will
  69. # allow. One of these connections will be reserved for a user with
  70. # SUPER privileges to allow the administrator to login even if the
  71. # connection limit has been reached.
  72. max_connections = 1000
  73.  
  74. # Maximum amount of errors allowed per host. If this limit is reached,
  75. # the host will be blocked from connecting to the MySQL server until
  76. # "FLUSH HOSTS" has been run or the server was restarted. Invalid
  77. # passwords and other errors during the connect phase result in
  78. # increasing this value. See the "Aborted_connects" status variable for
  79. # global counter.
  80. max_connect_errors = 20
  81.  
  82. # The number of open tables for all threads. Increasing this value
  83. # increases the number of file descriptors that mysqld requires.
  84. # Therefore you have to make sure to set the amount of open files
  85. # allowed to at least 4096 in the variable "open-files-limit" in
  86. # section [mysqld_safe]
  87. table_open_cache = 2048
  88.  
  89. # Enable external file level locking. Enabled file locking will have a
  90. # negative impact on performance, so only use it in case you have
  91. # multiple database instances running on the same files (note some
  92. # restrictions still apply!) or if you use other software relying on
  93. # locking MyISAM tables on file level.
  94. #external-locking
  95.  
  96. # The maximum size of a query packet the server can handle as well as
  97. # maximum query size server can process (Important when working with
  98. # large BLOBs).  enlarged dynamically, for each connection.
  99. max_allowed_packet = 16M
  100.  
  101. # The size of the cache to hold the SQL statements for the binary log
  102. # during a transaction. If you often use big, multi-statement
  103. # transactions you can increase this value to get more performance. All
  104. # statements from transactions are buffered in the binary log cache and
  105. # are being written to the binary log at once after the COMMIT.  If the
  106. # transaction is larger than this value, temporary file on disk is used
  107. # instead.  This buffer is allocated per connection on first update
  108. # statement in transaction
  109. binlog_cache_size = 1M
  110.  
  111. # Ecrit dans le log binaire apres chaque transaction, imperatif lors d'une config master pour eviter de perdre
  112. # trop de transactions lors d'un crash.
  113. # (0 = inactif, c'est l'OS qui gere le flush vers le log / 1 = Actif, MySQL force l'ecriture vers le log)
  114. # Tungsten needs 0
  115. # Galera needs 1
  116. sync_binlog             = 1
  117.  
  118. # Maximum allowed size for a single HEAP (in memory) table. This option
  119. # is a protection against the accidential creation of a very large HEAP
  120. # table which could otherwise use up all memory resources.
  121. max_heap_table_size = 64M
  122.  
  123. # Size of the buffer used for doing full table scans.
  124. # Allocated per thread, if a full scan is needed.
  125. read_buffer_size = 2M
  126.  
  127. # When reading rows in sorted order after a sort, the rows are read
  128. # through this buffer to avoid disk seeks. You can improve ORDER BY
  129. # performance a lot, if set this to a high value.
  130. # Allocated per thread, when needed.
  131. read_rnd_buffer_size = 16M
  132.  
  133. # Sort buffer is used to perform sorts for some ORDER BY and GROUP BY
  134. # queries. If sorted data does not fit into the sort buffer, a disk
  135. # based merge sort is used instead - See the "Sort_merge_passes"
  136. # status variable. Allocated per thread if sort is needed.
  137. sort_buffer_size = 32M
  138.  
  139. # This buffer is used for the optimization of full JOINs (JOINs without
  140. # indexes). Such JOINs are very bad for performance in most cases
  141. # anyway, but setting this variable to a large value reduces the
  142. # performance impact. See the "Select_full_join" status variable for a
  143. # count of full JOINs. Allocated per thread if full join is found
  144. join_buffer_size = 32M
  145.  
  146. # How many threads we should keep in a cache for reuse. When a client
  147. # disconnects, the client's threads are put in the cache if there aren't
  148. # more than thread_cache_size threads from before.  This greatly reduces
  149. # the amount of thread creations needed if you have a lot of new
  150. # connections. (Normally this doesn't give a notable performance
  151. # improvement if you have a good thread implementation.)
  152. thread_cache_size = 8
  153.  
  154. # This permits the application to give the threads system a hint for the
  155. # desired number of threads that should be run at the same time.  This
  156. # value only makes sense on systems that support the thread_concurrency()
  157. # function call (Sun Solaris, for example).
  158. # You should try [number of CPUs]*(2..4) for thread_concurrency
  159. thread_concurrency = 8
  160.  
  161.  
  162. # --- Query Cache
  163. # NON SUPPORTE PAR GALERA
  164. # Active / Desactive la prise en charge du cache requetes
  165. #query_cache_type       = 0
  166.  
  167. # Query cache is used to cache SELECT results and later return them
  168. # without actual executing the same query once again. Having the query
  169. # cache enabled may result in significant speed improvements, if your
  170. # have a lot of identical queries and rarely changing tables. See the
  171. # "Qcache_lowmem_prunes" status variable to check if the current value
  172. # is high enough for your load.
  173. # Note: In case your tables change very often or if your queries are
  174. # textually different every time, the query cache may result in a
  175. # slowdown instead of a performance improvement.
  176. #query_cache_size = 64M
  177.  
  178. # Only cache result sets that are smaller than this limit. This is to
  179. # protect the query cache of a very large result set overwriting all
  180. # other query results.
  181. #query_cache_limit = 8M
  182.  
  183. # Minimum word length to be indexed by the full text search index.
  184. # You might wish to decrease it if you need to search for shorter words.
  185. # Note that you need to rebuild your FULLTEXT index, after you have
  186. # modified this value.
  187. ft_min_word_len = 4
  188.  
  189. # If your system supports the memlock() function call, you might want to
  190. # enable this option while running MySQL to keep it locked in memory and
  191. # to avoid potential swapping out in case of high memory pressure. Good
  192. # for performance.
  193. #memlock
  194.  
  195. # Table type which is used by default when creating new tables, if not
  196. # specified differently during the CREATE TABLE statement.
  197. default-storage-engine = INNODB
  198.  
  199. # Thread stack size to use. This amount of memory is always reserved at
  200. # connection time. MySQL itself usually needs no more than 64K of
  201. # memory, while if you use your own stack hungry UDF functions or your
  202. # OS requires more stack for some operations, you might need to set this
  203. # to a higher value.
  204. thread_stack = 192K
  205.  
  206. # Set the default transaction isolation level. Levels available are:
  207. # READ-UNCOMMITTED, READ-COMMITTED, REPEATABLE-READ, SERIALIZABLE
  208. transaction_isolation = REPEATABLE-READ
  209.  
  210. # Maximum size for internal (in-memory) temporary tables. If a table
  211. # grows larger than this value, it is automatically converted to disk
  212. # based table This limitation is for a single table. There can be many
  213. # of them.
  214. tmp_table_size = 128M
  215.  
  216. # Enable binary logging. This is required for acting as a MASTER in a
  217. # replication configuration. You also need the binary log if you need
  218. # the ability to do point in time recovery from your latest backup.
  219. #log-bin=mysql-bin
  220. #log_bin = /var/lib/mysql/mysql-binary-log
  221.  
  222. # Nbre de jours apres lesquels les logs binaires sont purges
  223. expire_logs_days=7
  224.  
  225. # binary logging format - mixed recommended
  226. # Format des logs binaires pour la replication
  227. # Pour resumer, au 2011/12/07 Row Based est la methode la plus sure, mixed doit encore etre eprouve
  228. # cf http://www.slideshare.net/ligaya/mysql-51-replication
  229. # Galera needs ROW
  230. binlog_format=ROW
  231.  
  232. # If you're using replication with chained slaves (A->B->C), you need to
  233. # enable this option on server B. It enables logging of updates done by
  234. # the slave thread into the slave's binary log.
  235. #log_slave_updates
  236.  
  237. # Enable the full query log. Every query (even ones with incorrect
  238. # syntax) that the server receives will be logged. This is useful for
  239. # debugging, it is usually disabled in production use.
  240. #log
  241.  
  242. # Print warnings to the error log file.  If you have any problem with
  243. # MySQL you should enable logging of warnings and examine the error log
  244. # for possible explanations.
  245. #log_warnings
  246.  
  247. # Log slow queries. Slow queries are queries which take more than the
  248. # amount of time defined in "long_query_time" or which do not use
  249. # indexes well, if log_short_format is not enabled. It is normally good idea
  250. # to have this turned on if you frequently add new queries to the
  251. # system.
  252. slow_query_log
  253.  
  254. # Log des requetes lentes
  255. slow_query_log_file     = /var/log/mysql/mysql-slow-queries.log
  256.  
  257. # All queries taking more than this amount of time (in seconds) will be
  258. # trated as slow. Do not use "1" as a value here, as this will result in
  259. # even very fast queries being logged from time to time (as MySQL
  260. # currently measures time with second accuracy only).
  261. long_query_time = 5
  262.  
  263.  
  264.  
  265.  
  266.  
  267. # --- Logs
  268. # Log des requetes brutes (texte)
  269. general_log_file        = /var/log/mysql/mysql-request.log
  270. general_log             = 0
  271.  
  272. # Log d'erreur
  273. log_error               = /var/log/mysql/mysql-error.log
  274.  
  275. # Log des requetes n'utilisant pas d'index
  276. #log-queries-not-using-indexes
  277.  
  278. # Log de relay
  279. #relay_log               = mysql-relay-bin
  280.  
  281.  
  282.  
  283.  
  284.  
  285.  
  286.  
  287.  
  288. # ***  Replication related settings
  289.  
  290.  
  291. # Unique server identification number between 1 and 2^32-1. This value
  292. # is required for both master and slave hosts. It defaults to 1 if
  293. # "master-host" is not set, but will MySQL will not function as a master
  294. # if it is omitted.
  295. server-id = 1
  296.  
  297. # Replication Slave (comment out master section to use this)
  298. #
  299. # To configure this host as a replication slave, you can choose between
  300. # two methods :
  301. #
  302. # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
  303. #    the syntax is:
  304. #
  305. #    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
  306. #    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
  307. #
  308. #    where you replace <host>, <user>, <password> by quoted strings and
  309. #    <port> by the master's port number (3306 by default).
  310. #
  311. #    Example:
  312. #
  313. #    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
  314. #    MASTER_USER='joe', MASTER_PASSWORD='secret';
  315. #
  316. # OR
  317. #
  318. # 2) Set the variables below. However, in case you choose this method, then
  319. #    start replication for the first time (even unsuccessfully, for example
  320. #    if you mistyped the password in master-password and the slave fails to
  321. #    connect), the slave will create a master.info file, and any later
  322. #    changes in this file to the variable values below will be ignored and
  323. #    overridden by the content of the master.info file, unless you shutdown
  324. #    the slave server, delete master.info and restart the slaver server.
  325. #    For that reason, you may want to leave the lines below untouched
  326. #    (commented) and instead use CHANGE MASTER TO (see above)
  327. #
  328. # required unique id between 2 and 2^32 - 1
  329. # (and different from the master)
  330. # defaults to 2 if master-host is set
  331. # but will not function as a slave if omitted
  332. #server-id = 2
  333. #
  334. # The replication master for this slave - required
  335. #master-host = <hostname>
  336. #
  337. # The username the slave will use for authentication when connecting
  338. # to the master - required
  339. #master-user = <username>
  340. #
  341. # The password the slave will authenticate with when connecting to
  342. # the master - required
  343. #master-password = <password>
  344. #
  345. # The port the master is listening on.
  346. # optional - defaults to 3306
  347. #master-port = <port>
  348.  
  349. # Make the slave read-only. Only users with the SUPER privilege and the
  350. # replication slave thread will be able to modify data on it. You can
  351. # use this to ensure that no applications will accidently modify data on
  352. # the slave instead of the master
  353. #read_only
  354.  
  355.  
  356. #*** MyISAM Specific options
  357.  
  358.  
  359. # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
  360. # Do not set it larger than 30% of your available memory, as some memory
  361. # is also required by the OS to cache rows. Even if you're not using
  362. # MyISAM tables, you should still set it to 8-64M as it will also be
  363. # used for internal temporary disk tables.
  364. key_buffer_size = 32M
  365.  
  366. # MyISAM uses special tree-like cache to make bulk inserts (that is,
  367. # INSERT ... SELECT, INSERT ... VALUES (...), (...), ..., and LOAD DATA
  368. # INFILE) faster. This variable limits the size of the cache tree in
  369. # bytes per thread. Setting it to 0 will disable this optimisation.  Do
  370. # not set it larger than "key_buffer_size" for optimal performance.
  371. # This buffer is allocated when a bulk insert is detected.
  372. bulk_insert_buffer_size = 64M
  373.  
  374. # This buffer is allocated when MySQL needs to rebuild the index in
  375. # REPAIR, OPTIMIZE, ALTER table statements as well as in LOAD DATA INFILE
  376. # into an empty table. It is allocated per thread so be careful with
  377. # large settings.
  378. myisam_sort_buffer_size = 128M
  379.  
  380. # The maximum size of the temporary file MySQL is allowed to use while
  381. # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
  382. # If the file-size would be bigger than this, the index will be created
  383. # through the key cache (which is slower).
  384. myisam_max_sort_file_size = 10G
  385.  
  386. # If a table has more than one index, MyISAM can use more than one
  387. # thread to repair them by sorting in parallel. This makes sense if you
  388. # have multiple CPUs and plenty of memory.
  389. myisam_repair_threads = 1
  390.  
  391. # Automatically check and repair not properly closed MyISAM tables.
  392. myisam_recover
  393.  
  394. # *** INNODB Specific options ***
  395.  
  396. # Use this option if you have a MySQL server with InnoDB support enabled
  397. # but you do not plan to use it. This will save memory and disk space
  398. # and speed up some things.
  399. #skip-innodb
  400.  
  401. # Additional memory pool that is used by InnoDB to store metadata
  402. # information.  If InnoDB requires more memory for this purpose it will
  403. # start to allocate it from the OS.  As this is fast enough on most
  404. # recent operating systems, you normally do not need to change this
  405. # value. SHOW INNODB STATUS will display the current amount used.
  406. innodb_additional_mem_pool_size = 20M
  407.  
  408. # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
  409. # row data. The bigger you set this the less disk I/O is needed to
  410. # access data in tables. On a dedicated database server you may set this
  411. # parameter up to 80% of the machine physical memory size. Do not set it
  412. # too large, though, because competition of the physical memory may
  413. # cause paging in the operating system.  Note that on 32bit systems you
  414. # might be limited to 2-3.5G of user level memory per process, so do not
  415. # set it too high.
  416. innodb_buffer_pool_size = 16G
  417.  
  418. # InnoDB stores data in one or more data files forming the tablespace.
  419. # If you have a single logical drive for your data, a single
  420. # autoextending file would be good enough. In other cases, a single file
  421. # per device is often a good choice. You can configure InnoDB to use raw
  422. # disk partitions as well - please refer to the manual for more info
  423. # about this.
  424. innodb_data_file_path = ibdata1:10M:autoextend
  425.  
  426. # Set this option if you would like the InnoDB tablespace files to be
  427. # stored in another location. By default this is the MySQL datadir.
  428. #innodb_data_home_dir = <directory>
  429.  
  430. # Number of IO threads to use for async IO operations. This value is
  431. # hardcoded to 8 on Unix, but on Windows disk I/O may benefit from a
  432. # larger number.
  433. innodb_write_io_threads = 8
  434. innodb_read_io_threads = 8
  435.  
  436. # If you run into InnoDB tablespace corruption, setting this to a nonzero
  437. # value will likely help you to dump your tables. Start from value 1 and
  438. # increase it until you're able to dump the table successfully.
  439. #innodb_force_recovery=1
  440.  
  441. # Number of threads allowed inside the InnoDB kernel. The optimal value
  442. # depends highly on the application, hardware as well as the OS
  443. # scheduler properties. A too high value may lead to thread thrashing.
  444. innodb_thread_concurrency = 16
  445.  
  446. # If set to 1, InnoDB will flush (fsync) the transaction logs to the
  447. # disk at each commit, which offers full ACID behavior. If you are
  448. # willing to compromise this safety, and you are running small
  449. # transactions, you may set this to 0 or 2 to reduce disk I/O to the
  450. # logs. Value 0 means that the log is only written to the log file and
  451. # the log file flushed to disk approximately once per second. Value 2
  452. # means the log is written to the log file at each commit, but the log
  453. # file is only flushed to disk approximately once per second.
  454.  
  455. # Force l'ecriture des logs a chaque commit de transaction (valeur par defaut = 1)
  456. # http://dev.mysql.com/doc/refman/5.0/en/replication-howto-masterbaseconfig.html
  457. # 0 = log buffer written to log file + flush to disk on per second but nothing at transaction commit
  458. # 1 = log buffer + flush at every transaction commit
  459. # 2 = log buffer written to log file at every transaction commit + flush to disk every second
  460. # Tungsten needs 2
  461. # Galera needs 0 (see below in configuration Galera Specific needs)
  462. #innodb_flush_log_at_trx_commit = 1
  463.  
  464. # Speed up InnoDB shutdown. This will disable InnoDB to do a full purge
  465. # and insert buffer merge on shutdown. It may increase shutdown time a
  466. # lot, but InnoDB will have to do it on the next startup instead.
  467. #innodb_fast_shutdown
  468.  
  469. # The size of the buffer InnoDB uses for buffering log data. As soon as
  470. # it is full, InnoDB will have to flush it to disk. As it is flushed
  471. # once per second anyway, it does not make sense to have it very large
  472. # (even with long transactions).
  473. innodb_log_buffer_size = 256M
  474.  
  475. # Size of each log file in a log group. You should set the combined size
  476. # of log files to about 25%-100% of your buffer pool size to avoid
  477. # unneeded buffer pool flush activity on log file overwrite. However,
  478. # note that a larger logfile size will increase the time needed for the
  479. # recovery process.
  480. innodb_log_file_size = 2G
  481.  
  482. # Total number of files in the log group. A value of 2-3 is usually good
  483. # enough.
  484. innodb_log_files_in_group = 3
  485.  
  486. # Location of the InnoDB log files. Default is the MySQL datadir. You
  487. # may wish to point it to a dedicated hard drive or a RAID1 volume for
  488. # improved performance
  489. #innodb_log_group_home_dir
  490.  
  491. # Maximum allowed percentage of dirty pages in the InnoDB buffer pool.
  492. # If it is reached, InnoDB will start flushing them out agressively to
  493. # not run out of clean pages at all. This is a soft limit, not
  494. # guaranteed to be held.
  495. innodb_max_dirty_pages_pct = 90
  496.  
  497. # The flush method InnoDB will use for Log. The tablespace always uses
  498. # doublewrite flush logic. The default value is "fdatasync", another
  499. # option is "O_DSYNC".
  500. #innodb_flush_method=O_DSYNC
  501.  
  502. # How long an InnoDB transaction should wait for a lock to be granted
  503. # before being rolled back. InnoDB automatically detects transaction
  504. # deadlocks in its own lock table and rolls back the transaction. If you
  505. # use the LOCK TABLES command, or other transaction-safe storage engines
  506. # than InnoDB in the same transaction, then a deadlock may arise which
  507. # InnoDB cannot notice. In cases like this the timeout is useful to
  508. # resolve the situation.
  509. innodb_lock_wait_timeout = 120
  510.  
  511. # Demande a MySQL de stocker les donnees InnoDB ds des fichiers separes pour chaque table
  512. #innodb_file_per_table
  513.  
  514.  
  515.  
  516. # --- Plugins
  517. plugin_dir              = /usr/lib/mysql/plugin
  518.  
  519.  
  520. # --- Galera Specific Needs
  521. # http://www.codership.com/wiki/doku.php?id=configuration_tips
  522. innodb_autoinc_lock_mode                = 2
  523. innodb_locks_unsafe_for_binlog          = 1
  524. innodb_flush_log_at_trx_commit          = 0
  525. innodb_doublewrite                      = 0
  526.  
  527. wsrep_provider                          = /usr/lib/mysql/plugin/libgalera_smm.so
  528. wsrep_cluster_address                   = "gcomm://192.168.0.50:4567"
  529. #wsrep_cluster_address                  = "gcomm://"
  530. wsrep_sst_auth                          = cluster:blabla
  531. #wsrep_sst_method                       = rsync
  532. wsrep_sst_method                        = xtrabackup
  533. wsrep_provider_options                  = "gcache.size=2048M;gcache.page_size=2048M;"
  534. wsrep_sst_receive_address               = 192.168.0.49
  535. #wsrep_notify_cmd                       = "/scripts/mysql/wsrep_notify"
  536. wsrep_replicate_myisam                  = 1
  537. wsrep_slave_threads                     = 16
  538. wsrep_causal_reads                      = 1
  539.  
  540.  
  541.  
  542. [mysqldump]
  543. # Do not buffer the whole result set in memory before writing it to
  544. # file. Required for dumping very large tables
  545. quick
  546. max_allowed_packet = 16M
  547.  
  548.  
  549.  
  550.  
  551.  
  552. [mysql]
  553. no-auto-rehash
  554.  
  555. # Only allow UPDATEs and DELETEs that use keys.
  556. #safe-updates
  557.  
  558.  
  559.  
  560.  
  561.  
  562. [myisamchk]
  563. key_buffer_size = 512M
  564. sort_buffer_size = 512M
  565. read_buffer = 8M
  566. write_buffer = 8M
  567.  
  568.  
  569.  
  570.  
  571. [mysqlhotcopy]
  572. interactive-timeout
  573.  
  574.  
  575.  
  576.  
  577.  
  578.  
  579. [mysqld_safe]
  580. # Increase the amount of open files allowed per process. Warning: Make
  581. # sure you have set the global system limit high enough! The high value
  582. # is required for a large number of opened tables
  583. open-files-limit = 8192
  584.  
  585. # Permet a Galera de tester tour a tour les nodes specifies pour rejoindre le cluster au demarrage du noeud actuel
  586. wsrep_urls = "gcomm://192.168.0.50:4567,gcomm://192.168.0.51:4567"