Hi @sGendrot, this wouldn’t really work for n8n I am afraid
The reason is that changes to the database aren’t reflected by other instances until they are restarted. So if in your instance A you disable a workflow, this change would take effect immediately on instance A and is also written to the database.
However, instance B would not notice this change and would still assume the workflow is still active.
Could be an interesting feature request though (allow using multiple main instances in queue mode); I’ll convert your question into a feature request so you and other users can vote on it.
Just out of interest, have you hit any limits or problems with using a single main instance?
@sGendrot do all replicas need to be active at the same time or could you just run with an active-passive style setup and just fire it up if the other pod goes down?