Is your feature request related to a problem? Please describe.
Currently in an ACTIVE\WARM-PASSIVE cluster setup there is no way to prevent processing of tasks in the WARM-PASSIVE site.
Describe the solution you'd like
We suggest adding an interface, ISiteAwareness that will be checked for every push\pop\etc... and prevent operations from the in WARM-PASSIVE site.
Default implementation will be true - meaning your active. implementing the interface can be in an external module.
Describe alternatives you've considered
Forking Orkes Queues and maintaining a fork with site awareness support.
Is your feature request related to a problem? Please describe. Currently in an ACTIVE\WARM-PASSIVE cluster setup there is no way to prevent processing of tasks in the WARM-PASSIVE site.
Describe the solution you'd like We suggest adding an interface, ISiteAwareness that will be checked for every push\pop\etc... and prevent operations from the in WARM-PASSIVE site. Default implementation will be true - meaning your active. implementing the interface can be in an external module.
Describe alternatives you've considered Forking Orkes Queues and maintaining a fork with site awareness support.
WDYT?