| | 41 | On nodedb1, we need to set the group_replication_bootstrap_group variable tells a member that it shouldn’t expect to receive information from peers and should instead establish a new group and elect itself the primary member. You can turn this variable on with the following command: |
| | 42 | {{{ |
| | 43 | SET GLOBAL group_replication_bootstrap_group=ON; |
| | 44 | }}} |
| | 45 | Then you can start replication for the initial group member: |
| | 46 | {{{ |
| | 47 | START GROUP_REPLICATION; |
| | 48 | }}} |
| | 49 | Following that, you can set the group_replication_bootstrap_group variable back to OFF, since the only situation where this is appropriate is when there are no existing group members: |
| | 50 | {{{ |
| | 51 | SET GLOBAL group_replication_bootstrap_group=OFF; |
| | 52 | }}} |
| | 53 | The group will be started with this server as the only member. Verify this by checking the entries within the replication_group_members table in the performance_schema database: |
| | 54 | {{{ |
| | 55 | SELECT * FROM performance_schema.replication_group_members; |
| | 56 | }}} |