# How to remove peer info in Donor node
**URL:** https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612
**Category:** MySQL & MariaDB
**Tags:** mysql
**Created:** [November 17, 2022, 2:08am UTC](https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612 "2022-11-17T02:08:28Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@views\_eos](https://forums.percona.com/u/views_eos)
#### Post date: [November 17, 2022, 2:08am UTC](https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612/1 "2022-11-17T02:08:28Z")
– status info –
wsrep\_cluster\_name=‘g\_test1’
node1 - Donor (192.168.0.1)
node2 - New node (192.168.0.2)
Node2 was safely stopped after node1 and node2 joined successfully
However, node1 is constantly attempting to reconnect node2.
```auto
[Note] WSREP: (d45ecf8d, 'tcp://0.0.0.0:4567') reconnecting to d9b63250 (tcp://192.168.0.2:4567), attempt 48720
[Note] WSREP: (d45ecf8d, 'tcp://0.0.0.0:4567') reconnecting to d9b63250 (tcp://192.168.0.2:4567), attempt 48750
```
How to remove peer info (192.168.0.2) in Donor node?
I want stop trying reconnecting
Because, Node2 handshake fail when joining other cluster group (g\_test\_new)
# Node2 error log
```auto
[Note] WSREP: handshake failed, my group: 'g_test_new', peer group: 'g_test1'
```
---
### Author:  [@matthewb](https://forums.percona.com/u/matthewb)
#### Post date: [November 17, 2022, 1:32pm UTC](https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612/2 "2022-11-17T13:32:15Z")
> [@views\_eos](#):
>
> wsrep\_cluster\_name=‘g\_test1’
This should be the same for all nodes. If the name is not the same, then a node cannot join. node1 will continue to attempt to node2 because node2 had a failure condition.
You can force node1 back to bootstrap mode, which should stop connection attempts:
```
SET GLOBAL wsrep_provider_options='pc.bootstrap=YES';
```
---
### Author:  [@views\_eos](https://forums.percona.com/u/views_eos)
#### Post date: [November 23, 2022, 3:33am UTC](https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612/3 "2022-11-23T03:33:08Z")
Thank you for your kind reply
---
### Author:  [@views\_eos](https://forums.percona.com/u/views_eos)
#### Post date: [November 30, 2022, 7:55am UTC](https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612/4 "2022-11-30T07:55:09Z")
Sorry I tried to execute the command, but it didn’t work (ignore command)
I stopped node2 and ran the command on node1.
SET GLOBAL wsrep\_provider\_options=‘pc.bootstrap=YES’;
node1 error log
[Note] WSREP: Ignore ‘pc.bootstrap’ in PRIM
[Note] WSREP: (d45ecf8d, ‘tcp://0.0.0.0:4567’) reconnecting to d9b63250 (tcp://192.168.0.2:4567), attempt 1020
[Note] WSREP: (d45ecf8d, ‘tcp://0.0.0.0:4567’) reconnecting to d9b63250 (tcp://192.168.0.2:4567), attempt 1050
[Note] WSREP: (d45ecf8d, ‘tcp://0.0.0.0:4567’) reconnecting to d9b63250 (tcp://192.168.0.2:4567), attempt 1080
I hope Node1 forgets Node2
---
### Author:  [@matthewb](https://forums.percona.com/u/matthewb)
#### Post date: [November 30, 2022, 4:28pm UTC](https://forums.percona.com/t/how-to-remove-peer-info-in-donor-node/18612/5 "2022-11-30T16:28:04Z")
Can you `SET GLOBAL wsrep_cluster_address=gcomm://` or is that read-only? If that is read-only, then you must restart node1 to make it forget about node2. It will never forget on its own.