NDB Cluster Configuration Files Type Integer Default Value 32 Minimum Value 7 Maximum Value 32 This variable indicates the number of least significant bits within the 32-bit  server_id  which actually identify the server. Indicating that the server is actually identified by fewer than 32 bits makes it possible for some of the remaining bits to be used for other purposes, such as storing user data generated by applications using the NDB API’s Event API within the  AnyValue  of an  OperationOptions  structure (NDB Cluster uses the  AnyValue  to store the server ID). When extracting the effective server ID from  server_id  for purposes such as detection of replication loops, the server ignores the remaining bits. The  server_id_bits  variable is used to mask out any irrelevant bits of  server_id  in the I/O and SQL threads when deciding whether an event should be ignored based on the server ID. This data can be read from the binary log by  mysqlbinlog , provided that it is run with its own server_id_bits  variable set to 32 (the default). If the value of  server_id  greater than or equal to 2 to the power of  server_id_bits ; otherwise, mysqld  refuses to start. This system variable is supported only by NDB Cluster. It is not supported in the standard MySQL 8.0 Server. Setting this variable has an effect only when using replication with the  NDB  storage engine; in MySQL Server 8.0, it is present but does nothing. For more information, see Section 23.6.6, “Starting NDB Cluster Replication (Single Replication Channel)” . Whether or not batched updates are enabled on NDB Cluster replicas. 4194 System Variable transaction_allow_batching Scope Session Dynamic Yes SET_VAR  Hint Applies No Type Boolean Command-Line Format --slave-allow-batching[={OFF|ON}] System Variable slave_allow_batching Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value OFF • slave_allow_batching • transaction_allow_batching