(Netapp issue) New IP addresses of cluster members do not propagate #300

New Issue

Closed

opened 2022-05-09 09:17:27 +00:00 by lx · 0 comments

lx commented

2022-05-09 09:17:27 +00:00

Owner

We have a live cluster over three distant sites. One of the sites had to change IP addresses due to an ISP change. Reconfiguring all nodes of the other sites to talk to these nodes properly was a pain, as netapp did not propagate the new IPs correctly via gossiping, as it would have been expected to.

We have a live cluster over three distant sites. One of the sites had to change IP addresses due to an ISP change. Reconfiguring all nodes of the other sites to talk to these nodes properly was a pain, as netapp did not propagate the new IPs correctly via gossiping, as it would have been expected to.

lx added the

label 2022-05-09 09:17:27 +00:00

lx referenced this issue from a commit

2022-05-09 10:09:17 +00:00

Update netapp to 0.4.4, fix #300

lx referenced a pull request that will close this issue

2022-05-09 10:09:40 +00:00

Update netapp to 0.4.4, fix #300 #301

lx closed this issue

2022-05-09 11:35:27 +00:00

Sign in to join this conversation.

No Label

S3 Compatibility

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#300

No description provided.