No cache version.

Caching disabled. Default setting for this page:enabled (code DEF204)
If the display is too slow, you can disable the user mode to view the cached version.

Rechercher dans le manuel MySQL

13.4.3.6 Functions to Inspect and Set the Group Replication Communication Protocol Version

The following functions enable you to inspect and configure the Group Replication communication protocol version that is used by a replication group.

  • group_replication_get_communication_protocol()

    Inspect the Group Replication communication protocol version that is currently in use for a group.

    Syntax: 

    STRING group_replication_get_communication_protocol()

    This function has no parameters.

    Return value:

    The oldest MySQL Server version that can join this group and use the group's communication protocol. Versions from MySQL 5.7.14 allow compression of messages, and versions from MySQL 8.0.16 also allow fragmentation of messages. Note that the group_replication_get_communication_protocol() UDF returns the minimum MySQL version that the group supports, which might differ from the version number that was passed to the group_replication_set_communication_protocol() UDF, and from the MySQL Server version that is installed on the member where you use the UDF.

    If the protocol cannot be inspected because this server instance does not belong to a replication group, an error is returned as a string.

    Example:

    1. SELECT group_replication_get_communication_protocol();
    2. +------------------------------------------------+
    3. | group_replication_get_communication_protocol() |
    4. +------------------------------------------------+
    5. | 8.0.16                                         |
    6. +------------------------------------------------+

    For more information, see Section 18.4.1.4, “Setting a Group's Communication Protocol Version”.

  • group_replication_set_communication_protocol()

    Downgrade the Group Replication communication protocol version of a group so that members at earlier releases can join, or upgrade the Group Replication communication protocol version of a group after upgrading MySQL Server on all members. The GROUP_REPLICATION_ADMIN privilege is required to use this UDF, and all existing group members must be online when you issue the statement, with no loss of majority.

    Note

    For MySQL InnoDB cluster, the communication protocol version is managed automatically whenever the cluster topology is changed using AdminAPI operations. You do not have to use these UDFs yourself for an InnoDB cluster.

    Syntax: 

    STRING group_replication_set_communication_protocol(version)

    Arguments:

    • version: For a downgrade, specify the MySQL Server version of the prospective group member that has the oldest installed server version. In this case, the command makes the group fall back to a communication protocol compatible with that server version if possible. The minimum server version that you can specify is MySQL 5.7.14. For an upgrade, specify the new MySQL Server version to which the existing group members have been upgraded.

    Return value:

    A string containing the result of the operation, for example whether it was successful or not.

    Example:

    1. SELECT group_replication_set_communication_protocol("5.7.25");

    For more information, see Section 18.4.1.4, “Setting a Group's Communication Protocol Version”.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-group-replication-functions-for-communication-protocol.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut