ALTER LOGFILE GROUP Statement EVENT  statement. If you rotate the binary log master key because you suspect that the current or any of the previous binary log master keys might have been compromised, issue the statement on every applicable source and replica server, which enables you to verify immediate compliance. For additional  ALTER INSTANCE ROTATE BINLOG MASTER KEY  usage information, including what to do if the process does not complete correctly or is interrupted by an unexpected server halt, see Section 17.3.2, “Encrypting Binary Log Files and Relay Log Files” . This action reconfigures a TLS context from the current values of the system variables that define the context. It also updates the status variables that reflect the active context values. This action requires the CONNECTION_ADMIN  privilege. For additional information about reconfiguring the TLS context, including which system and status variables are context-related, see Server-Side Runtime Configuration and Monitoring for Encrypted Connections. By default, the statement reloads the TLS context for the main connection interface. If the  FOR CHANNEL  clause (available as of MySQL 8.0.21) is given, the statement reloads the TLS context for the named channel:  mysql_main  for the main connection interface,  mysql_admin  for the administrative connection interface. For information about the different interfaces, see Section 5.1.12.1, “Connection Interfaces” . The updated TLS context properties are exposed in the Performance Schema tls_channel_status  table. See Section 27.12.21.7, “The tls_channel_status Table” . Updating the TLS context for the main interface may also affect the administrative interface because unless some nondefault TLS value is configured for that interface, it uses the same TLS context as the main interface. By default, the  RELOAD TLS  action rolls back with an error and has no effect if the configuration values do not permit creation of the new TLS context. The previous context values continue to be used for new connections. If the optional  NO ROLLBACK ON ERROR  clause is given and the new context cannot be created, rollback does not occur. Instead, a warning is generated and encryption is disabled for new connections on the interface to which the statement applies. ALTER INSTANCE RELOAD TLS  statements are not written to the binary log (and thus are not replicated). TLS configuration is local and depends on local files not necessarily present on all servers involved. • ALTER INSTANCE RELOAD TLS • ALTER INSTANCE RELOAD KEYRING If a keyring component is installed, this action tells the component to re-read its configuration file and reinitialize any keyring in-memory data. If you modify the component configuration at runtime, the new configuration does not take effect until you perform this action. Keyring reloading requires the ENCRYPTION_KEY_ADMIN  privilege. This action was added in MySQL 8.0.24. This action enables reconfiguring only the currently installed keyring component. It does not enable changing which component is installed. For example, if you change the configuration for the installed keyring component,  ALTER INSTANCE RELOAD KEYRING  causes the new configuration to take effect. On the other hand, if you change the keyring component named in the server manifest file,  ALTER INSTANCE RELOAD KEYRING  has no effect and the current component remains installed. ALTER INSTANCE RELOAD KEYRING  statements are not written to the binary log (and thus are not replicated). 13.1.6 ALTER LOGFILE GROUP Statement ALTER LOGFILE GROUP  logfile_group 2479