Replication and Binary Logging Options and Variables Default Value Value of --tmpdir The name of the directory where the replica creates temporary files. Setting this variable takes effect for all replication channels immediately, including running channels. The variable value is by default equal to the value of the  tmpdir  system variable, or the default that applies when that system variable is not specified. When the replication SQL thread replicates a  LOAD DATA  statement, it extracts the file to be loaded from the relay log into temporary files, and then loads these into the table. If the file loaded on the source is huge, the temporary files on the replica are huge, too. Therefore, it might be advisable to use this option to tell the replica to put temporary files in a directory located in some file system that has a lot of available space. In that case, the relay logs are huge as well, so you might also want to set the relay_log  system variable to place the relay logs in that file system. The directory specified by this option should be located in a disk-based file system (not a memory-based file system) so that the temporary files used to replicate  LOAD DATA  statements can survive machine restarts. The directory also should not be one that is cleared by the operating system during the system startup process. However, replication can now continue after a restart if the temporary files have been removed. • slave_max_allowed_packet Command-Line Format --slave-max-allowed-packet=# System Variable slave_max_allowed_packet Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 1073741824 Minimum Value 1024 Maximum Value 1073741824 Block Size 1024 This option sets the maximum packet size in bytes that the replication SQL and I/O threads can handle. Setting this variable takes effect for all replication channels immediately, including running channels. It is possible for a source to write binary log events longer than its  max_allowed_packet  setting once the event header is added. The setting for  slave_max_allowed_packet  must be larger than the max_allowed_packet  setting on the source, so that large updates using row-based replication do not cause replication to fail. This global variable always has a value that is a positive integer multiple of 1024; if you set it to some value that is not, the value is rounded down to the next highest multiple of 1024 for it is stored or used; setting  slave_max_allowed_packet  to 0 causes 1024 to be used. (A truncation warning is issued in all such cases.) The default and maximum value is 1073741824 (1 GB); the minimum is 1024. Command-Line Format --slave-net-timeout=# System Variable slave_net_timeout Scope Global 3531 • slave_net_timeout