github-starred/zfs-ha
2
0
Fork 0
mirror of https://github.com/ewwhite/zfs-ha.git synced 2026-05-15 14:16:09 -06:00
Code Issues 11 Projects Packages Wiki Activity Actions

[GH-ISSUE #37] Spread ZFS Pools across nodes #35

New issue
Open
opened 2026-05-05 03:32:14 -06:00 by gitea-mirror · 3 comments
gitea-mirror commented 2026-05-05 03:32:14 -06:00
Owner
Copy link

Originally created by @rbicelli on GitHub (Apr 3, 2021).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/37

Hi, could I create various group resources (group-vol1, group-vol2, group-vol3, gruop-vol4) and spread them across cluster nodes?

Originally created by @rbicelli on GitHub (Apr 3, 2021). Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/37 Hi, could I create various group resources (group-vol1, group-vol2, group-vol3, gruop-vol4) and spread them across cluster nodes?
gitea-mirror commented 2026-05-05 03:32:19 -06:00
Author
Owner
Copy link

@ewwhite commented on GitHub (Apr 3, 2021):

Yes, you can have different pools assigned to different cluster nodes. A common set up with two hosts is to run one pool and host one, and another pool on host two. It’s a way of leveraging all the resources available and having reasonable failover in the event of a node’s unavailability.

Edmund White

On Apr 3, 2021, at 2:44 PM, Riccardo @.***> wrote:



Hi, could I create various group resources (group-vol1, group-vol2, group-vol3, gruop-vol4) and spread them across cluster nodes?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ewwhite/zfs-ha/issues/37, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABJSFNX2WY7BIIBCEYVKAQ3TG5VYZANCNFSM42KSCA3Q.

<!-- gh-comment-id:812916804 --> @ewwhite commented on GitHub (Apr 3, 2021): Yes, you can have different pools assigned to different cluster nodes. A common set up with two hosts is to run one pool and host one, and another pool on host two. It’s a way of leveraging all the resources available and having reasonable failover in the event of a node’s unavailability. Edmund White On Apr 3, 2021, at 2:44 PM, Riccardo ***@***.***> wrote:  Hi, could I create various group resources (group-vol1, group-vol2, group-vol3, gruop-vol4) and spread them across cluster nodes? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://github.com/ewwhite/zfs-ha/issues/37>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABJSFNX2WY7BIIBCEYVKAQ3TG5VYZANCNFSM42KSCA3Q>.
gitea-mirror commented 2026-05-05 03:32:21 -06:00
Author
Owner
Copy link

@rbicelli commented on GitHub (Apr 15, 2021):

And could it work using 2 SAS controllers per host connecting each to different chains?
Like
Controller 1 Host 1 -> Enclosure Chain 1
Controller 1 Host 2 -> Enclosure Chain 1
Controller 2 Host 1 -> Enclosure Chain 2
Controller 2 Host 2 -> Enclosure Chain 2

each node serving 2 volumes per chain?

<!-- gh-comment-id:820575392 --> @rbicelli commented on GitHub (Apr 15, 2021): And could it work using 2 SAS controllers per host connecting each to different chains? Like Controller 1 Host 1 -> Enclosure Chain 1 Controller 1 Host 2 -> Enclosure Chain 1 Controller 2 Host 1 -> Enclosure Chain 2 Controller 2 Host 2 -> Enclosure Chain 2 each node serving 2 volumes per chain?
gitea-mirror commented 2026-05-05 03:32:24 -06:00
Author
Owner
Copy link

@almereyda commented on GitHub (Oct 11, 2022):

In Kubernetes environments, one can also leverage OpenEBS cStor for replicated pools across multiple nodes:

<!-- gh-comment-id:1273945001 --> @almereyda commented on GitHub (Oct 11, 2022): In Kubernetes environments, one can also leverage OpenEBS cStor for replicated pools across multiple nodes: - https://github.com/mayadata-io/cstor/wiki/Using-uZFS-for-storing-cStor-Volume-Data > cStor Data engine makes it possible to run ZFS in user space and use a collection of such ZFS instances running on multiple nodes to provide a replicated storage resilient against node failures.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#35
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?