# Tiebreaker follows primary feature?
**URL:** https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675
**Category:** General
**Tags:** linstor, drbd
**Created:** [March 17, 2025, 4:59pm UTC](https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675 "2025-03-17T16:59:45Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@dori](https://forums.linbit.com/u/dori)
#### Post date: [March 17, 2025, 4:59pm UTC](https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675/1 "2025-03-17T16:59:45Z")
Hi all!
I’m using linstor on two locations (let’s call them datacenters 😉 ) in active/active mode. Performance is great. I tag nodes with aux properties to get resources deployed to both availability zones (datacenters/locations). Everything works just fine, except when I move a vm to the other site, I have to move the tiebreaker for its disk resource manually to the other site also in order to preserve the quorum and be able to continue to run the vm in case of inter-site connection failure. Not a big deal, I made some cron scripts for that. But it would be great, if linstor would have a feature to move the tiebreaker together with the primary to the node with the same aux property (parameter) when the primary moves.
---
### Author:  [@kermat](https://forums.linbit.com/u/kermat)
#### Post date: [March 20, 2025, 7:03pm UTC](https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675/2 "2025-03-20T19:03:36Z")
Unless you are automatically failing over VMs between sites you could safely disable quorum all together. The problem you’re describing boils down to the two sites being unable to provide quorum in a meaningful way. Generally, you want quorum enabled to prevent split-brains in HA clusters, but if there’s no automated failover, then an admin would have to promote a peer (start a VM) while the DRBD devices were disconnected in order to introduce a split-brain.
---
### Author:  [@dori](https://forums.linbit.com/u/dori)
#### Post date: [March 21, 2025, 6:54pm UTC](https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675/3 "2025-03-21T18:54:20Z")
Thanks, will try it. Is there any disadvantages to have quorum disabled in this case?
---
### Author:  [@kermat](https://forums.linbit.com/u/kermat)
#### Post date: [April 23, 2025, 7:55pm UTC](https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675/4 "2025-04-23T19:55:27Z")
Sorry for the delay, vacations and busy in between. No drawbacks that I can think of given what you’ve shared. Have you been able to test this?
---
### Author:  [@dori](https://forums.linbit.com/u/dori)
#### Post date: [April 26, 2025, 8:46am UTC](https://forums.linbit.com/t/tiebreaker-follows-primary-feature/675/5 "2025-04-26T08:46:57Z")
Yes I have tested it on a few resources. I have set auto-quorum=disabled,quorum=off and auto-add-quorum-tiebreaker=false on resource definition. Everything works as expected. The only thing I find strange is that after every migration rd property auto-add-quorum-tiebreaker get set back to True. Doesn’t affect the function though. I’m using the linstor-proxmox plugin.