This page documents system variables related to Galera Cluster. For options that are not system variables, see . See for a complete list of system variables and instructions on setting them. Also see the .
wsrep_allowlistDescription:
Allowed IP addresses, comma-delimited.
Note that setting gmcast.listen_addr=tcp://[::]:4567 on a dual-stack system (for instance, Linux with net.ipv6.bindv6only = 0), IPv4 addresses need to be allow-listed using the IPv4-mapped IPv6 address (eg. ::ffff:1.2.3.4).
Command line: --wsrep-allowlist=value1[,value2...]
Scope: Global
Dynamic: No
Data Type: String
Default Value: None
Introduced:
wsrep_applier_retry_countDescription: Maximum number of applier retry attempts. Previously, replication applying always stopped for the first non-ignored failure occurring in event applying, and the node emergency-aborts (or start inconsistency voting). Some failures, however, can be concurrency related, and applying may succeed if the operation is tried at later time. This variable controls the retry-applying feature. It is set to 0 by default, which means no retrying.
Command line: --wsrep-applier-retry-count=value
Scope: Global
wsrep_auto_increment_controlDescription: If set to 1 (the default), automatically adjusts the and variables according to the size of the cluster, and readjusts them when the cluster size changes. This avoids replication conflicts due to . In a primary-replica environment, can be set to OFF.
Command line: --wsrep-auto-increment-control[={0|1}]
Scope: Global
wsrep_causal_readsDescription: If set to ON (OFF is default), enforces characteristics across the cluster. In the case that a primary applies an event more quickly than a replica, the two could briefly be out-of-sync. With this variable set to ON, the replica will wait for the event to be applied before processing further queries. Setting to ON also results in larger read latencies. Deprecated by .
Command line: --wsrep-causal-reads[={0|1}]
wsrep_certificate_expiration_hours_warning This variable is documented in detail here:
wsrep_certification_rulesDescription: Certification rules to use in the cluster. Possible values are:
strict: Stricter rules that could result in more certification failures. For example with foreign keys, certification failure could result if different nodes receive non-conflicting insertions at about the same time that point to the same row in a parent table.
optimized: Relaxed rules that allow more concurrency and cause less certification failures.
wsrep_certify_nonPKDescription: When set to ON (the default), Galera still certifies transactions for tables with no . However, this can still cause undefined behavior in some circumstances. It is recommended to define primary keys for every InnoDB table when using Galera.
Command line: --wsrep-certify-nonPK[={0|1}]
Scope: Global
wsrep_cluster_addressDescription: The addresses of cluster nodes to connect to when starting up.
Good practice is to specify all possible cluster nodes, in the form gcomm://<node1 or ip:port>,<node2 or ip2:port>,<node3 or ip3:port>.
Specifying an empty ip (gcomm://) will cause the node to start a new cluster (which should not be done in the my.cnf file, as after each restart the server will not rejoin the current cluster).
wsrep_cluster_nameDescription: The name of the cluster. Nodes cannot connect to clusters with a different name, so needs to be identical on all nodes in the same cluster. The variable can be set dynamically, but note that doing so may be unsafe and cause an outage, and that the wsrep provider is unloaded and loaded.
Command line: --wsrep-cluster-name=value
Scope: Global
Dynamic: Yes
wsrep_convert_LOCK_to_trxDescription: Converts / statements to and . Used mainly for getting older applications to work with a multi-primary setup, use carefully, as can result in extremely large writesets.
Command line: --wsrep-convert-LOCK-to-trx[={0|1}]
Scope: Global
Dynamic: Yes
wsrep_data_home_dirDescription: Directory where wsrep provider will store its internal files.
Command line: --wsrep-data-home-dir=value
Scope: Global
Dynamic: No
wsrep_dbug_optionDescription: Unused. The mechanism to pass the DBUG options to the wsrep provider hasn't been implemented.
Command line: --wsrep-dbug-option=value
Scope: Global
Dynamic: Yes
wsrep_debugDescription: WSREP debug level logging.
Before MariaDB 10.6.1, DDL logging was only logged on the originating node. From , it is logged on other nodes as well.
Data type is . Valid values are:
0: NONE
wsrep_desyncDescription: When a node receives more write-sets than it can apply, the transactions are placed in a received queue. If the node's received queue has too many write-sets waiting to be applied (as defined by the WSREP provider option), then the node would usually engage Flow Control. However, when this option is set to ON, Flow Control will be disabled for the desynced node. The desynced node works through the received queue until it reaches a more manageable size. The desynced node continues to receive write-sets from the other nodes in the cluster. The other nodes in the cluster do not wait for the desynced node to catch up, so the desynced node can fall even further behind the other nodes in the cluster. You can check if a node is desynced by checking if the status variable is equal to Donor/Desynced.
Command line: --wsrep-desync[={0|1}]
wsrep_dirty_readsDescription: By default, when not synchronized with the group (=OFF), a node rejects all queries other than SET and SHOW. If wsrep_dirty_reads is set to 1, queries which do not change data, like SELECT queries (dirty reads), creating of prepare statement, and so forth will be accepted by the node.
Command line: --wsrep-dirty-reads[={0|1}]
wsrep_drupal_282555_workaroundDescription: If set to ON, a workaround for is enabled. This is a bug where, in some cases, when inserting a DEFAULT value into an column, a duplicate key error may be returned.
Command line: --wsrep-drupal-282555-workaround[={0|1}]
Scope: Global
wsrep_forced_binlog_formatDescription: A that overrides any session binlog format settings.
Command line: --wsrep-forced-binlog-format=value
Scope: Global
Dynamic: Yes
wsrep_gtid_domain_idDescription: This system variable defines the domain ID that is used for .
When is set to ON, wsrep_gtid_domain_id is used in place of for all Galera Cluster write sets.
When is set to OFF, wsrep_gtid_domain_id
wsrep_gtid_modeDescription: attempts to keep consistent for Galera Cluster write sets on all cluster nodes. state is initially copied to a joiner node during an . If you are planning to use Galera Cluster with , then wsrep GTID mode can be helpful.
When wsrep_gtid_mode is set to ON, is used in place of for all Galera Cluster write sets.
When wsrep_gtid_mode
wsrep_gtid_seq_noDescription: Internal server usage, manually set WSREP GTID seqno.
Command line: None
Scope: Session only
Dynamic: Yes
wsrep_ignore_apply_errorsDescription: Bitmask determining whether errors are ignored, or reported back to the provider.
0: No errors are skipped.
1: Ignore some DDL errors (DROP DATABASE, DROP TABLE, DROP INDEX, ALTER TABLE).
wsrep_load_data_splittingDescription: If set to ON, supports big data files by introducing transaction splitting. The setting has been deprecated in Galera 4, and defaults to OFF
Command line: --wsrep-load-data-splitting[={0|1}]
Scope: Global
wsrep_log_conflictsDescription: If set to ON (OFF is default), details of conflicting MDL as well as InnoDB locks in the cluster will be logged.
Command line: --wsrep-log-conflicts[={0|1}]
Scope: Global
wsrep_max_ws_rowsDescription: Maximum permitted number of rows per write set. The support for this variable has been added and in order to be backward compatible. The default value has been changed to 0, which essentially allows write sets to be any size.
Command line: --wsrep-max-ws-rows=#
Scope: Global
wsrep_max_ws_sizeDescription: Maximum permitted size in bytes per write set. Write sets exceeding 2GB are rejected.
Command line: --wsrep-max-ws-size=#
Scope: Global
Dynamic: Yes
wsrep_modeDescription: Turns on WSREP features which are not part of the default behavior.
BINLOG_ROW_FORMAT_ONLY: Only ROW is supported.
DISALLOW_LOCAL_GTID: Nodes can have GTIDs for local transactions in a number of scenarios. If
wsrep_mysql_replication_bundleDescription: Determines the number of replication events that are grouped together. Experimental implementation aimed to assist with bottlenecks when a single replica faces a large commit time delay. If set to 0 (the default), there is no grouping.
Command line: --wsrep-mysql-replication-bundle=#
Scope: Global
wsrep_node_addressDescription: Specifies the node's network address, in the format ip address[:port]. It supports IPv6. The default behavior is for the node to pull the address of the first network interface on the system and the default Galera port. This automatic guessing can be unreliable, particularly in the following cases:
Cloud deployments
Container deployments
wsrep_node_incoming_addressDescription: This is the address from which the node listens for client connections. If an address is not specified or it's set to AUTO (default), mysqld uses either or , or tries to get one from the list of available network interfaces, in the same order. See also .
Command line: --wsrep-node-incoming-address=value
Scope: Global
wsrep_node_nameDescription: Name of this node. This name can be used in as a preferred donor. Note that multiple nodes in a cluster can have the same name.
Command line: --wsrep-node-name=value
Scope: Global
Dynamic: Yes
wsrep_notify_cmdDescription: Command to be executed each time the node state or the cluster membership changes. Can be used for raising an alarm, configuring load balancers and so on. See the for more details.
Command line: --wsrep-notify-command=value
Scope: Global
Dynamic: No
wsrep_onDescription: Whether or not wsrep replication is enabled. If the global value is set to OFF , it is not possible to load the provider and join the node in the cluster. If only the session value is set to OFF, the operations from that particular session are not replicated in the cluster, but other sessions and applier threads will continue as normal. The session value of the variable does not affect the node's membership and thus, regardless of its value, the node keeps receiving updates from other nodes in the cluster. It is set to OFF by default and must be turned on to enable Galera replication.
Command line: --wsrep-on[={0|1}]
wsrep_OSU_methodDescription: Online schema upgrade method. The default is TOI, specifying the setting without the optional parameter will set to RSU.
TOI: Total Order Isolation. In each cluster node, DDL is processed in the same order regarding other transactions, guaranteeing data consistency. However, affected parts of the database will be locked for the whole cluster.
RSU
wsrep_patch_versionDescription: Wsrep patch version, for example wsrep_25.10.
Command line: None
Scope: Global
Dynamic: No
wsrep_providerDescription: Location of the wsrep library, usually /usr/lib/libgalera_smm.so on Debian and Ubuntu, and /usr/lib64/libgalera_smm.so on Red Hat/CentOS.
Command line: --wsrep-provider=value
Scope: Global
wsrep_provider_optionsDescription: Semicolon (;) separated list of wsrep options (see ).
Command line: --wsrep-provider-options=value
Scope: Global
More details can be found on this page:
wsrep_recoverDescription: If set to ON when the server starts, the server will recover the sequence number of the most recent write set applied by Galera, and it will be output to stderr, which is usually redirected to the . At that point, the server will exit. This sequence number can be provided to the system variable.
Command line: --wsrep-recover[={0|1}]
Scope: Global
wsrep_reject_queriesDescription: Variable to set to reject queries from client connections, useful for maintenance. The node continues to apply write-sets, but an Error 1047: Unknown command error is generated by a client query.
NONE - Not set. Queries are processed as normal.
ALL - All queries from client connections will be rejected, but existing client connections are maintained.
wsrep_replicate_myisamDescription: Whether or not DML updates for tables will be replicated. This functionality is still experimental and should not be relied upon in production systems. Deprecated in , and removed in , use instead.
Command line: --wsrep-replicate-myisam[={0|1}]
Scope: Global
wsrep_restart_slaveDescription: If set to ON, the replica is restarted automatically, when node joins back to cluster.
Command line: --wsrep-restart-slave[={0|1}]
Scope: Global
Dynamic: Yes
wsrep_retry_autocommitDescription: Number of times autocommited queries are retried due to cluster-wide conflicts before returning an error to the client. If set to 0, no retries are attempted, while a value of 1 (the default) or more specifies the number of retries attempted. Can be useful to assist applications using autocommit to avoid deadlocks.
Reasons for failures include:
Certification failure: If the transaction reached the replication state and observed the conflict by performing a certification test.
High-priority abort: If the execution of the transaction was interrupted by the replication applier before entering the replication state.
wsrep_slave_FK_checksDescription: If set to ON (the default), the applier replica thread performs foreign key constraint checks.
Command line: --wsrep-slave-FK-checks[={0|1}]
Scope: Global
Dynamic: Yes
wsrep_slave_threadsDescription: Number of replica threads used to apply Galera write sets in parallel. The Galera replica threads are able to determine which write sets are safe to apply in parallel. However, if your cluster nodes seem to have frequent consistency problems, then setting the value to 1 will probably fix the problem. See for more information.
Command line: --wsrep-slave-threads=#
Scope: Global
wsrep_slave_UK_checksDescription: If set to ON, the applier replica thread performs secondary index uniqueness checks.
Command line: --wsrep-slave-UK-checks[={0|1}]
Scope: Global
Dynamic: Yes
wsrep_sr_storeDescription: Storage for streaming replication fragments.
Command line: --wsrep-sr-store=val
Scope: Global
Dynamic: No
wsrep_ssl_mode This variable is documented in details on this page:
wsrep_sst_authDescription: Username and password of the user to use for replication. Unused if is set to rsync, while for other methods it should be in the format <user>:<password>. The contents are masked in logs and when querying the value with . See for more information.
Command line: --wsrep-sst-auth=value
Scope: Global
wsrep_sst_donorDescription: Comma-separated list (from 5.5.33) or name (as per ) of the servers as donors, or the source of the state transfer, in order of preference. The donor-selection algorithm, in general, prefers a donor capable of transferring only the missing transactions (IST) to the joiner node, instead of the complete state (SST). Thus, it starts by looking for an IST-capable node in the given donor list followed by rest of the nodes in the cluster. In case multiple candidate nodes are found outside the specified donor list, the node in the same segment () as the joiner is preferred. If none of the existing nodes in the cluster can serve the missing transactions through IST, the algorithm moves on to look for a suitable node to transfer the entire state (SST). It first looks at the nodes specified in the donor list (irrespective of their segment). If no suitable donor is still found, the rest of the donor nodes are checked for suitability only if the donor list has a "terminating-comma". Note that a stateless node (the Galera arbitrator) can never be a donor. See for more information.
Command line: --wsrep-sst-donor=value
Scope: Global
Dynamic: Yes (read note above)
Data Type: String
wsrep_sst_donor_rejects_queriesDescription: If set to ON (OFF is default), the donor node will reject incoming queries, returning an UNKNOWN COMMAND error code. Can be used for informing load balancers that a node is unavailable.
Command line: --wsrep-sst-donor-rejects-queries[={0|1}]
Scope: Global
wsrep_sst_methodDescription: Method used for taking the . See for more information.
Command line: --wsrep-sst-method=value
Scope: Global
Dynamic: Yes
See this page for more information about this variable:
wsrep_sst_receive_addressDescription: This is the address where other nodes (donor) in the cluster connect to in order to send the state-transfer updates. If an address is not specified or its set to AUTO (default), mysqld uses 's value as the receiving address. However, if is not set, it uses address from either or tries to get one from the list of available network interfaces, in the same order. Note: setting it to localhost will make it impossible for nodes running on other hosts to reach this node. See for more information.
Command line: --wsrep-sst-receive-address=value
wsrep_start_positionDescription: The start position that the node should use in the format: UUID:seq_no. The proper value to use for this position can be recovered with .
Command line: --wsrep-start-position=value
Scope: Global
wsrep_status_fileDescription: wsrep status output filename.
Command line: --wsrep-status-file=value
Scope: Global
Dynamic: No
wsrep_strict_ddlDescription: If set, reject DDL statements on affected tables not supporting Galera replication. This is done by checking if the table is InnoDB, which is the only table currently fully supporting Galera replication. MyISAM tables will not trigger the error if the experimental setting is ON. If set, should be set on all tables in the cluster. Affected DDL statements include: (e.g. CREATE TABLE t1(a int) engine=Aria)
Statements in , , and are permitted as the affected
tables are only known at execution. Furthermore, the various USER, ROLE, SERVER and
DATABASE statements are also allowed as they do not have an affected table. Deprecated in and removed in . Use instead.
Command line: --wsrep-strict-ddl[={0|1}
wsrep_sync_waitDescription: Setting this variable ensures causality checks will take place before executing an operation of the type specified by the value, ensuring that the statement is executed on a fully synced node. While the check is taking place, new queries are blocked on the node to allow the server to catch up with all updates made in the cluster up to the point where the check was begun. Once reached, the original query is executed on the node. This can result in higher latency. Note that when is ON, values of wsrep_sync_wait become irrelevant. Sample usage (for a critical read that must have the most up-to-date data) SET SESSION wsrep_sync_wait=1; SELECT ...; SET SESSION wsrep_sync_wait=0;
0 - Disabled (default)
wsrep_trx_fragment_sizeDescription: Size of transaction fragments for streaming replication (measured in units as specified by )
Command line: --wsrep-trx-fragment-size=#
Scope: Session
Dynamic: Yes
wsrep_trx_fragment_unitDescription: Unit for streaming replication transaction fragments' size:
bytes: transaction’s binlog events buffer size in bytes
rows: number of rows affected by the transaction
This page is licensed: CC BY-SA / Gnu FDL
Dynamic: Yes
Data Type: INT UNSIGNED
Default Value: 0
Range: 0 to 4294967295
Introduced:
Dynamic: Yes
Data Type: Boolean
Default Value: ON
Scope: Session
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Removed:
Command line: --wsrep-certifcation-rules
Scope: Global
Dynamic: Yes
Data Type: Enumeration
Default Value: strict
Valid Values: strict, optimized
Data Type: Boolean
Default Value: ON
The variable can be changed at runtime in some configurations, and will result in the node closing the connection to any current cluster, and connecting to the new address.
If specifying a port, note that this is the Galera port, not the MariaDB port.
For example:
gcomm://192.168.0.1,192.168.0.2,192.168.0.3
gcomm://192.168.0.1:1234,192.168.0.2:1234,192.168.0.3:1234?gmcast.listen_addr=tcp://0.0.0.0:1234
See also gmcast.listen_addr
Command line: --wsrep-cluster-address=value
Scope: Global
Dynamic: No
Data Type: String
Data Type: String
Default Value: my_wsrep_cluster
Data Type: Boolean
Default Value: OFF
Data Type: String
Default Value: The variable value.
Data Type: String
1: SERVER: MariaDB server code contains WSREP_DEBUG log writes, and these are added to server error log.
2: TRANSACTION: Logging from wsrep-lib transaction is added to the error log.
3: STREAMING: Logging from streaming transactions in wsrep-lib is added to the error log.
4: CLIENT: Logging from wsrep-lib client state is added to the error log.
Command line: --wsrep-debug[={NONE|SERVER|TRANSACTION|STREAMING|CLIENT}]
Scope: Global
Dynamic: Yes
Data Type: Enumeration
Default Value: NONE
Valid Values: NONE, SERVER, TRANSACTION, STREAMING, CLIENT
Scope: Global
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Scope: Global,Session
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Valid Values: ON, OFF
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Default Value: NONE
Data Type: Enum
Valid Values: STATEMENT, ROW, MIXED or NONE (which resets the forced binlog format state).
There are some additional requirements that need to be met in order for this mode to generate consistent . For more information, see Using MariaDB GTIDs with MariaDB Galera Cluster.
Command line: --wsrep-gtid-domain-id=#
Scope: Global
Dynamic: Yes
Data Type: numeric
Default Value: 0
Range: 0 to 4294967295
OFFThere are some additional requirements that need to be met in order for this mode to generate consistent . For more information, see Using MariaDB GTIDs with MariaDB Galera Cluster.
Command line: --wsrep-gtid-mode[={0|1}]
Scope: Global
Dynamic: Yes
Data Type: boolean
Default Value: OFF
Data Type: numeric
Range: 0 to 18446744073709551615
Introduced:
2: Skip DML errors (Only ignores DELETE errors).
4: Ignore all DDL errors.
Command line: --wsrep-ignore-apply-errors
Scope: Global
Dynamic: Yes
Data Type: Numeric
Default Value: 7
Range: 0 to 7
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Deprecated: MariaDB 10.4.2
Removed:
Data Type: Boolean
Default Value: OFF
Data Type: Numeric
Default Value: 0
Range: 0 to 1048576
Data Type: Numeric
Default Value: 2147483647 (2GB)
Range: 1024 to 2147483647
DISALLOW_LOCAL_GTIDERROR HY000: Galera replication not supportedA DDL statement is executed with wsrep_OSU_method=RSU set.
A DML statement writes to a non-InnoDB table.
A DML statement writes to an InnoDB table with wsrep_on=OFF set.
REPLICATE_ARIA: Whether or not DML updates for tables will be replicated. This functionality is experimental and should not be relied upon in production systems.
REPLICATE_MYISAM: Whether or not DML updates for a tables will be replicated. This functionality is experimental and should not be relied upon in production systems.
REQUIRED_PRIMARY_KEY: Table should have PRIMARY KEY defined.
STRICT_REPLICATION: Same as the old wsrep_strict_ddl setting.
SKIP_APPLIER_FK_CHECKS_IN_IST: When this operation mode is set, and the node is processing IST or catch-up, appliers skip FK checking. See this page for details.
This flag is available from MariaDB 12.0.
Command line: --wsrep-mode=value
Scope: Global
Dynamic: Yes
Data Type: Enumeration
Default Value: (Empty)
Valid Values: SKIP_APPLIER_FK_CHECKS_IN_IST, BINLOG_ROW_FORMAT_ONLY, DISALLOW_LOCAL_GTID, REQUIRED_PRIMARY_KEY, REPLICATE_ARIA, REPLICATE_MYISAM and STRICT_REPLICATION
Introduced:
Data Type: Numeric
Default Value: 0
Range: 0 to 1000
Servers running multiple nodes
Network address translation (NAT)
Clusters with nodes in more than one region
Command line: --wsrep-node-address=value
Scope: Global
Dynamic: No
Data Type: String
Default Value: Primary network address, usually eth0 with a default port of 4567, or 0.0.0.0 if no IP address.
Dynamic: No
Data Type: String
Default Value: AUTO
Data Type: String
Default Value: The server's hostname.
Data Type: String
Default Value: Empty
Scope: Global, Session
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Valid Values: ON, OFF
Command line: --wsrep-OSU-method[=value]
Scope: Global, Session
Dynamic: Yes
Data Type: Enum
Default Value: TOI
Valid Values: TOI, RSU
Data Type: String
Default Value: None
Default Value: None
Data Type: String
Default Value: Empty
Dynamic: No
Data Type: Boolean
Default Value: OFF
ALL_KILL All queries from client connections will be rejected, and existing client connections, including the current one, are immediately killed.
Command line: --wsrep-reject-queries[=value]
Scope: Global
Dynamic: Yes
Data Type: Enum
Default Value: NONE
Valid Values: NONE, ALL, ALL_KILL
Default Value: OFF
Data Type: Boolean
Valid Values: ON, OFF
Deprecated:
Removed:
Default Value: OFF
Data Type: Boolean
Command line: --wsrep-retry-autocommit=value
Scope: Global
Dynamic: No
Data Type: Numeric
Default Value: 1
Range: 0 to 10000
Data Type: Boolean
Default Value: ON
Dynamic: Yes
Data Type: Numeric
Default Value: 1
Range: 1 to 512
Data Type: Boolean
Default Value: OFF
Data Type: Enum
Default Value: table
Valid Values: table, none
Dynamic: Yes
Data Type: String
Default Value: (Empty)
Default Value:
Dynamic: Yes
Data Type: Boolean
Default Value: OFF
Data Type: String
Default Value: rsync
Valid Values: rsync, mysqldump, xtrabackup, xtrabackup-v2, mariadb-backup
Dynamic: Yes
Data Type: String
Default Value: AUTO
Data Type: String
Default Value: 00000000-0000-0000-0000-000000000000:-1
Data Type: String
Default Value: None
Introduced:
Scope: Global
Dynamic: Yes
Data Type: boolean
Default Value: OFF
Introduced:
Deprecated:
Removed:
1 - READ (SELECT and BEGIN/START TRANSACTION). This is the same as wsrep_causal_reads=1.2 - UPDATE and DELETE;
3 - READ, UPDATE and DELETE;
4 - INSERT and REPLACE;
5 - READ, INSERT and REPLACE;
6 - UPDATE, DELETE, INSERT and REPLACE;
7 - READ, UPDATE, DELETE, INSERT and REPLACE;
8 - SHOW
9 - READ and SHOW
10 - UPDATE, DELETE and SHOW
11 - READ, UPDATE, DELETE and SHOW
12 - INSERT, REPLACE and SHOW
13 - READ, INSERT, REPLACE and SHOW
14 - UPDATE, DELETE, INSERT, REPLACE and SHOW
15 - READ, UPDATE, DELETE, INSERT, REPLACE and SHOW
Command line: --wsrep-sync-wait=#
Scope: Session
Dynamic: Yes
Data Type: Numeric
Default Value: 0
Range:
0 to 15
Data Type: numeric
Default Value: 0
Range: 0 to 2147483647
statements: number of SQL statements executed in the multi-statement transactionCommand line: --wsrep-trx-fragment-unit=value
Scope: Session
Dynamic: Yes
Data Type: enum
Default Value: bytes
Valid Values: bytes, rows or statements