config.toml.example 4.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys in the current session. These statements are not affected by tidb_read_staleness. • Start an interactive transaction in the current session. Queries within this transaction still read the latest data param- eter. 11.9.2.2.4 Step 3: Execute the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys

provides the following MySQL-compatible timeout control parameters. • wait_timeout, controls the non-interactive idle timeout for the connection to Java applications. Since TiDB v5.4, the default value of wait_timeout earlier than v5.4, the default value is 0, which means the timeout is unlimited. • interactive_timeout, controls the interactive idle timeout for the connection to Java applications. The value is 8 hours by config.toml.example 5.4.1.4 Step 4. Run the deployment command Note: You can use secret keys or interactive passwords for security authentication when you deploy TiDB using TiUP: • If you use secret keys