# Advanced scheduling for Share Manager **URL:** \ **Category:** SUSE Storage\ **Created:** [March 7, 2021, 11:18pm UTC](https://forums.suse.com/t/advanced-scheduling-for-share-manager/19717 "2021-03-07T23:18:03Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![awelsman](https://avatars.discourse-cdn.com/v4/letter/a/a587f6/32.png) [@awelsman](https://forums.suse.com/u/awelsman)\ **Post date:** [March 7, 2021, 11:18pm UTC](https://forums.suse.com/t/advanced-scheduling-for-share-manager/19717/1 "2021-03-07T23:18:03Z")
I have a cluster with a number of nodes (EC2 instances) which, under considerable load, can die and be cycled back into the cluster by RKE. I want to run Longhorn on both those nodes and a few other, much more reliable ones. I have three nodes dedicated to Longhorn, one in each availability zone, and am storing my RWX volume replicas there. I can attach my volume to one of these dedicated nodes, but the moment I mount the volume to a deployment by using a PVC, the volume attaches to any random node Longhorn is installed on, not necessarily the one I selected through the UI. Is there any way I can reliably schedule the Share Manager pod to a given dedicated node? I realize the drawbacks with high availability and NFS, but would like to avoid running the pod on any of my more unreliable nodes. Thank you! ---
**Author:** ![PhanLe0110](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/phanle0110/32/7022_2.png) [@PhanLe0110](https://forums.suse.com/u/PhanLe0110)\ **Post date:** [March 11, 2021, 11:59pm UTC](https://forums.suse.com/t/advanced-scheduling-for-share-manager/19717/2 "2021-03-11T23:59:12Z")
Currently Longhorn doesn’t allow users to specify node selector or node affinity for the share manager pod. However, I think that you have presented a good use case for it. Can you file a GitHub enhancement issue? [https://github.com/longhorn/longhorn/issues/new/choose](https://github.com/longhorn/longhorn/issues/new/choose) ---
**Author:** ![rob.mengert](https://avatars.discourse-cdn.com/v4/letter/r/41988e/32.png) [@rob.mengert](https://forums.suse.com/u/rob.mengert)\ **Post date:** [May 20, 2024, 4:58pm UTC](https://forums.suse.com/t/advanced-scheduling-for-share-manager/19717/3 "2024-05-20T16:58:49Z")
Just want to confirm that this feature still does not exist before opening an enhancement issue as I have another use case that would benefit from this feature. ---
**Author:** ![DulexSteve](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@DulexSteve](https://forums.suse.com/u/DulexSteve)\ **Post date:** [June 8, 2024, 11:44am UTC](https://forums.suse.com/t/advanced-scheduling-for-share-manager/19717/4 "2024-06-08T11:44:03Z")
> [@awelsman](#): > > I have a cluster with a number of nodes (EC2 instances) which, under considerable load, can die and be cycled back into the cluster by RKE. I want to run Longhorn on both those nodes and a few other, much more reliable ones. I have three nodes dedicated to Longhorn, one in each availability zone, and am storing my RWX volume replicas there. I can attach my volume to one of these dedicated nodes, but the moment I mount the volume to a deployment by using a PVC, the volume attaches to any random node Longhorn is installed on, not necessarily the one I selected through the UI. > > Is there any way I can reliably schedule the Share Manager pod to a given dedicated node? I realize the drawbacks with high availability and NFS, but would like to avoid running the pod on any of my more unreliable nodes. How can I maintain a balance between high availability requirements and the need to ensure critical components like the Share Manager pod are consistently hosted on reliable nodes within my cluster?