Rechercher dans le manuel MySQL
17.1.6.1 Replication and Binary Logging Option and Variable Reference
The following two lists provide basic information about the MySQL command-line options and system variables applicable to replication and the binary log.
The command-line options and system variables in the following list relate to replication masters and replication slaves. Section 17.1.6.2, “Replication Master Options and Variables”, provides more detailed information about options and variables relating to replication master servers. For more information about options and variables relating to replication slaves, see Section 17.1.6.3, “Replication Slave Options and Variables”.
abort-slave-event-count
: Option used by mysql-test for debugging and testing of replicationauto_increment_increment
: AUTO_INCREMENT columns are incremented by this valueauto_increment_offset
: Offset added to AUTO_INCREMENT columnsbinlog_expire_logs_seconds
: Purge binary logs after this many secondsbinlog_gtid_simple_recovery
: Controls how binary logs are iterated during GTID recoveryCom_change_master
: Count of CHANGE MASTER TO statementsCom_show_master_status
: Count of SHOW MASTER STATUS statementsCom_show_slave_hosts
: Count of SHOW SLAVE HOSTS statementsCom_show_slave_status
: Count of SHOW SLAVE STATUS statementsCom_slave_start
: Count of START SLAVE statementsCom_slave_stop
: Count of STOP SLAVE statementsdisconnect-slave-event-count
: Option used by mysql-test for debugging and testing of replicationenforce-gtid-consistency
: Prevents execution of statements that cannot be logged in a transactionally safe mannerenforce_gtid_consistency
: Prevents execution of statements that cannot be logged in a transactionally safe mannerexpire_logs_days
: Purge binary logs after this many daysgtid-executed-compression-period
: Compress gtid_executed table each time this many transactions have occurred. 0 means never compress this table. Applies only when binary logging is disabled.gtid-mode
: Controls whether GTID based logging is enabled and what type of transactions the logs can containgtid_executed
: Global: All GTIDs in the binary log (global) or current transaction (session). Read-only.gtid_executed_compression_period
: Compress gtid_executed table each time this many transactions have occurred. 0 means never compress this table. Applies only when binary logging is disabled.gtid_mode
: Controls whether GTID based logging is enabled and what type of transactions the logs can containgtid_next
: Specifies the GTID for the next statement to execute; see documentation for detailsgtid_owned
: The set of GTIDs owned by this client (session), or by all clients, together with the thread ID of the owner (global). Read-only.gtid_purged
: The set of all GTIDs that have been purged from the binary loginit_slave
: Statements that are executed when a slave connects to a masterlog-bin-trust-function-creators
: If equal to 0 (the default), then when --log-bin is used, creation of a stored function is allowed only to users having the SUPER privilege and only if the function created does not break binary logginglog_builtin_as_identified_by_password
: Whether to log CREATE/ALTER USER, GRANT in backward-compatible fashionlog_statements_unsafe_for_binlog
: Disables error 1592 warnings being written to the error logmaster-info-file
: The location and name of the master info log as a file (deprecated)master-info-repository
: Whether to write master status information and replication I/O thread location in the master's binary logs to a table or file (deprecated)master-retry-count
: Number of tries the slave makes to connect to the master before giving upmaster_info_repository
: Whether to write master status information and replication I/O thread location in the master's binary logs to a table or a file (deprecated)max_relay_log_size
: If nonzero, relay log is rotated automatically when its size exceeds this value. If zero, size at which rotation occurs is determined by the value of max_binlog_size.original_commit_timestamp
: The time when a transaction was committed on the original masterimmediate_server_version
: The MySQL Server release number of the server that is the immediate master in a replication topologyoriginal_server_version
: The MySQL Server release number of the server where a transaction was originally committedrelay-log
: The location and base name to use for relay logsrelay-log-index
: The location and name to use for the file that keeps a list of the last relay logsrelay-log-info-file
: The location and name of the relay log info log as a file (deprecated)relay-log-info-repository
: Whether to write the replication SQL thread's location in the relay logs to a table or a file (deprecated)relay-log-recovery
: Enables automatic recovery of relay log files from master at startuprelay_log_basename
: Complete path to relay log, including filenamerelay_log_index
: The name of the relay log index filerelay_log_info_file
: The name of the file in which the slave records information about the relay logsrelay_log_info_repository
: Whether to write the replication SQL thread's location in the relay logs to a file or a tablerelay_log_purge
: Determines whether relay logs are purgedrelay_log_recovery
: Whether automatic recovery of relay log files from master at startup is enabled; must be enabled for a crash-safe slaverelay_log_space_limit
: Maximum space to use for all relay logsreplicate-do-db
: Tells the slave SQL thread to restrict replication to the specified databasereplicate-do-table
: Tells the slave SQL thread to restrict replication to the specified tablereplicate-ignore-db
: Tells the slave SQL thread not to replicate to the specified databasereplicate-ignore-table
: Tells the slave SQL thread not to replicate to the specified tablereplicate-rewrite-db
: Updates to a database with a different name than the originalreplicate-same-server-id
: In replication, if enabled, do not skip events having our server idreplicate-wild-do-table
: Tells the slave thread to restrict replication to the tables that match the specified wildcard patternreplicate-wild-ignore-table
: Tells the slave thread not to replicate to the tables that match the given wildcard patternreport-host
: Host name or IP of the slave to be reported to the master during slave registrationreport-password
: An arbitrary password that the slave server should report to the master. Not the same as the password for the MySQL replication user account.report-port
: Port for connecting to slave reported to the master during slave registrationreport-user
: An arbitrary user name that a slave server should report to the master. Not the same as the name used with the MySQL replication user account.Rpl_semi_sync_master_clients
: Number of semisynchronous slavesrpl_semi_sync_master_enabled
: Whether semisynchronous replication is enabled on the masterRpl_semi_sync_master_net_avg_wait_time
: The average time the master waited for a slave replyRpl_semi_sync_master_net_wait_time
: The total time the master waited for slave repliesRpl_semi_sync_master_net_waits
: The total number of times the master waited for slave repliesRpl_semi_sync_master_no_times
: Number of times the master turned off semisynchronous replicationRpl_semi_sync_master_no_tx
: Number of commits not acknowledged successfullyRpl_semi_sync_master_status
: Whether semisynchronous replication is operational on the masterRpl_semi_sync_master_timefunc_failures
: Number of times the master failed when calling time functionsrpl_semi_sync_master_timeout
: Number of milliseconds to wait for slave acknowledgmentrpl_semi_sync_master_trace_level
: The semisynchronous replication debug trace level on the masterRpl_semi_sync_master_tx_avg_wait_time
: The average time the master waited for each transactionRpl_semi_sync_master_tx_wait_time
: The total time the master waited for transactionsRpl_semi_sync_master_tx_waits
: The total number of times the master waited for transactionsrpl_semi_sync_master_wait_for_slave_count
: How many slave acknowledgments the master must receive per transaction before proceedingrpl_semi_sync_master_wait_no_slave
: Whether master waits for timeout even with no slavesrpl_semi_sync_master_wait_point
: The wait point for slave transaction receipt acknowledgmentRpl_semi_sync_master_wait_pos_backtraverse
: The total number of times the master waited for an event with binary coordinates lower than events waited for previouslyRpl_semi_sync_master_wait_sessions
: Number of sessions currently waiting for slave repliesRpl_semi_sync_master_yes_tx
: Number of commits acknowledged successfullyrpl_semi_sync_slave_enabled
: Whether semisynchronous replication is enabled on slaveRpl_semi_sync_slave_status
: Whether semisynchronous replication is operational on slaverpl_semi_sync_slave_trace_level
: The semisynchronous replication debug trace level on the slaverpl_read_size
: Set the minimum amount of data in bytes that is read from the binary log files and relay log filesrpl_stop_slave_timeout
: Set the number of seconds that STOP SLAVE waits before timing outserver_uuid
: The server's globally unique ID, automatically (re)generated at server startshow-slave-auth-info
: Show user name and password in SHOW SLAVE HOSTS on this masterskip-slave-start
: If set, slave is not autostartedslave-checkpoint-group
: Maximum number of transactions processed by a multithreaded slave before a checkpoint operation is called to update progress status. Not supported by NDB Cluster.slave-checkpoint-period
: Update progress status of multithreaded slave and flush relay log info to disk after this number of milliseconds. Not supported by NDB Cluster.slave-load-tmpdir
: The location where the slave should put its temporary files when replicating a LOAD DATA statementslave-max-allowed-packet
: Maximum size, in bytes, of a packet that can be sent from a replication master to a slave; overrides max_allowed_packetslave-net-timeout
: Number of seconds to wait for more data from a master/slave connection before aborting the readslave-parallel-type
: Tells the slave to use timestamp information (LOGICAL_CLOCK) or database partioning (DATABASE) to parallelize transactions. The default is LOGICAL_CLOCK.slave-parallel-workers
: Number of applier threads for executing replication transactions in parallel. The default is 4 applier threads. Set to 0 to disable slave multithreading. Not supported by MySQL Cluster.slave-pending-jobs-size-max
: Maximum size of slave worker queues holding events not yet appliedslave-rows-search-algorithms
: Deprecated, use the default settingslave-skip-errors
: Tells the slave thread to continue replication when a query returns an error from the provided listslave_checkpoint_group
: Maximum number of transactions processed by a multithreaded slave before a checkpoint operation is called to update progress status. Not supported by NDB Cluster.slave_checkpoint_period
: Update progress status of multithreaded slave and flush relay log info to disk after this number of milliseconds. Not supported by NDB Cluster.slave_compressed_protocol
: Use compression of master/slave protocolslave_exec_mode
: Allows for switching the slave thread between IDEMPOTENT mode (key and some other errors suppressed) and STRICT mode; STRICT mode is the default, except for NDB Cluster, where IDEMPOTENT is always usedSlave_heartbeat_period
: The slave's replication heartbeat interval, in secondsSlave_last_heartbeat
: Shows when the latest heartbeat signal was received, in TIMESTAMP formatslave_max_allowed_packet
: Maximum size, in bytes, of a packet that can be sent from a replication master to a slave; overrides max_allowed_packetSlave_open_temp_tables
: Number of temporary tables that the slave SQL thread currently has openslave_parallel_type
: Tells the slave to use timestamp information (LOGICAL_CLOCK) or database partioning (DATABASE) to parallelize transactions.slave_parallel_workers
: Number of applier threads for executing replication transactions in parallel. A value of 0 disables slave multithreading. Not supported by MySQL Cluster.slave_pending_jobs_size_max
: Maximum size of slave worker queues holding events not yet appliedslave_preserve_commit_order
: Ensures that all commits by slave workers happen in the same order as on the master to maintain consistency when using parallel applier threads.Slave_received_heartbeats
: Number of heartbeats received by a replication slave since previous resetSlave_retried_transactions
: The total number of times since startup that the replication slave SQL thread has retried transactionsslave_rows_search_algorithms
: Deprecated, use the default settingSlave_rows_last_search_algorithm_used
: Search algorithm most recently used by this slave to locate rows for row-based replication (index, table, or hash scan)Slave_running
: The state of this server as a replication slave (slave I/O thread status)slave_transaction_retries
: Number of times the slave SQL thread will retry a transaction in case it failed with a deadlock or elapsed lock wait timeout, before giving up and stoppingslave_type_conversions
: Controls type conversion mode on replication slave. Value is a list of zero or more elements from the list: ALL_LOSSY, ALL_NON_LOSSY. Set to an empty string to disallow type conversions between master and slave.sql_log_bin
: Controls binary logging for the current sessionsql_slave_skip_counter
: Number of events from the master that a slave server should skip. Not compatible with GTID replication.sync_master_info
: Synchronize master.info to disk after every #th eventsync_relay_log
: Synchronize relay log to disk after every #th eventsync_relay_log_info
: Synchronize relay.info file to disk after every #th eventtransaction_write_set_extraction
: Defines the algorithm used to hash the writes extracted during a transaction
The command-line options and system variables in the following list relate to the binary log. Section 17.1.6.4, “Binary Logging Options and Variables”, provides more detailed information about options and variables relating to binary logging. For additional general information about the binary log, see Section 5.4.4, “The Binary Log”.
binlog-checksum
: Enable/disable binary log checksumsbinlog-do-db
: Limits binary logging to specific databasesbinlog_format
: Specifies the format of the binary logbinlog-ignore-db
: Tells the master that updates to the given database should not be logged to the binary logbinlog-row-event-max-size
: Binary log max event sizebinlog_encryption
: Enable encryption for binary log files and relay log files on this serverbinlog_rotate_encryption_master_key_at_startup
: Rotate the binary log master key at server startupBinlog_cache_disk_use
: Number of transactions that used a temporary file instead of the binary log cachebinlog_cache_size
: Size of the cache to hold the SQL statements for the binary log during a transactionBinlog_cache_use
: Number of transactions that used the temporary binary log cachebinlog_checksum
: Enable/disable binary log checksumsbinlog_direct_non_transactional_updates
: Causes updates using statement format to nontransactional engines to be written directly to binary log. See documentation before using.binlog_error_action
: Controls what happens when the server cannot write to the binary logbinlog_group_commit_sync_delay
: Sets the number of microseconds to wait before synchronizing transactions to diskbinlog_group_commit_sync_no_delay_count
: Sets the maximum number of transactions to wait for before aborting the current delay specified by binlog_group_commit_sync_delaybinlog_max_flush_queue_time
: How long to read transactions before flushing to binary logbinlog_order_commits
: Whether to commit in same order as writes to binary logbinlog_row_image
: Use full or minimal images when logging row changesbinlog_row_metadata
: Configures the amount of table related metadata binary logged when using row-based logging.binlog_row_value_options
: Enables binary logging of partial JSON updates for row-based replication.binlog_rows_query_log_events
: When enabled, enables logging of rows query log events when using row-based logging. Disabled by default. Do not enable when producing logs for pre-5.6 slaves/readers.Binlog_stmt_cache_disk_use
: Number of nontransactional statements that used a temporary file instead of the binary log statement cachebinlog_stmt_cache_size
: Size of the cache to hold nontransactional statements for the binary log during a transactionBinlog_stmt_cache_use
: Number of statements that used the temporary binary log statement cachebinlog_transaction_dependency_tracking
: Source of dependency information (commit timestamps or transaction write sets) from which to assess which transactions can be executed in parallel by slave's multithreaded applier.binlog_transaction_dependency_history_size
: Number of row hashes kept for looking up transaction that last updated some row.Com_show_binlog_events
: Count of SHOW BINLOG EVENTS statementsCom_show_binlogs
: Count of SHOW BINLOGS statementslog-bin
: Specifies the base name for binary log fileslog-bin-index
: Specifies the name for the binary log index filelog-bin-use-v1-row-events
: Deprecated, use the default setting OFFlog-slave-updates
: Tells the slave to log the updates performed by its SQL thread to its own binary loglog_bin
: Whether the binary log is enabledlog_bin_basename
: Path and base name for binary log fileslog_bin_use_v1_row_events
: Deprecated, use the default setting OFFlog_slave_updates
: Whether the slave should log the updates performed by its SQL thread to its own binary log. Read-only; set using the --log-slave-updates server option.master-verify-checksum
: Cause master to examine checksums when reading from the binary logmaster_verify_checksum
: Cause master to read checksums from binary logmax-binlog-dump-events
: Option used by mysql-test for debugging and testing of replicationmax_binlog_cache_size
: Can be used to restrict the total size used to cache a multi-statement transactionmax_binlog_size
: Binary log will be rotated automatically when size exceeds this valuemax_binlog_stmt_cache_size
: Can be used to restrict the total size used to cache all nontransactional statements during a transactionslave-sql-verify-checksum
: Cause slave to examine checksums when reading from the relay logslave_sql_verify_checksum
: Cause slave to examine checksums when reading from relay logsporadic-binlog-dump-fail
: Option used by mysql-test for debugging and testing of replicationsync_binlog
: Synchronously flush binary log to disk after every #th event
For a listing of all command-line options, system and status variables used with mysqld, see Section 5.1.4, “Server Option, System Variable, and Status Variable Reference”.
Nederlandse vertaling
U hebt gevraagd om deze site in het Nederlands te bezoeken. Voor nu wordt alleen de interface vertaald, maar nog niet alle inhoud.Als je me wilt helpen met vertalingen, is je bijdrage welkom. Het enige dat u hoeft te doen, is u op de site registreren en mij een bericht sturen waarin u wordt gevraagd om u toe te voegen aan de groep vertalers, zodat u de gewenste pagina's kunt vertalen. Een link onderaan elke vertaalde pagina geeft aan dat u de vertaler bent en heeft een link naar uw profiel.
Bij voorbaat dank.
Document heeft de 26/06/2006 gemaakt, de laatste keer de 26/10/2018 gewijzigd
Bron van het afgedrukte document:https://www.gaudry.be/nl/mysql-rf-replication-options-reference.html
De infobrol is een persoonlijke site waarvan de inhoud uitsluitend mijn verantwoordelijkheid is. De tekst is beschikbaar onder CreativeCommons-licentie (BY-NC-SA). Meer info op de gebruiksvoorwaarden en de auteur.
Referenties
Deze verwijzingen en links verwijzen naar documenten die geraadpleegd zijn tijdens het schrijven van deze pagina, of die aanvullende informatie kunnen geven, maar de auteurs van deze bronnen kunnen niet verantwoordelijk worden gehouden voor de inhoud van deze pagina.
De auteur Deze site is als enige verantwoordelijk voor de manier waarop de verschillende concepten, en de vrijheden die met de referentiewerken worden genomen, hier worden gepresenteerd. Vergeet niet dat u meerdere broninformatie moet doorgeven om het risico op fouten te verkleinen.