[GH-ISSUE #41] [question] why colocation is not considered? #40

Open
opened 2026-05-05 03:32:52 -06:00 by gitea-mirror · 0 comments
Owner

Originally created by @mpeterson on GitHub (Feb 28, 2025).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/41

hey @ewwhite , I was wondering why your setup didn't include colocation?

If I understand correctly in the cases where the fence and resources run on two different nodes in a two node cluster it could lead to a situation where access to resources running the resource group is lost and cannot be fenced since the fencing agent is running in the other node.

Out of your deeper knowledgem, Is this an actual issue and should be addressed by colocation?

Originally created by @mpeterson on GitHub (Feb 28, 2025). Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/41 hey @ewwhite , I was wondering why your setup didn't include [colocation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_high_availability_clusters/assembly_colocating-cluster-resources.adoc_configuring-and-managing-high-availability-clusters)? If I understand correctly in the cases where the fence and resources run on two different nodes in a two node cluster it could lead to a situation where access to resources running the resource group is lost and cannot be fenced since the fencing agent is running in the other node. Out of your deeper knowledgem, Is this an actual issue and should be addressed by colocation?
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
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: github-starred/zfs-ha#40
No description provided.