Master gate — disabling stops all cross-server operations
Fallback
Mutual container fallback between nodes
Rsync on handback
Writeback rsync when the covered host recovers and containers return
Loading…
Nodes
Loading…
Fallback coverage
Loading…
Which of this host's containers the partner starts when this host goes dark. Anything already deployed there — the auth and arr stacks — never goes down, so it takes no tier.
Tier 1 is immediate; later tiers wait out the delays set in this host's conf.
To change what the partner hands to us, open this page there.
Loading…
Quick settings
Check interval
How often the daemon re-tests the partner. Also the age at which a state file is stale.
seconds
Handback strikes
Consecutive healthy checks before handing services back. Higher rides out a flapping link.
consecutive
Partnership suspend after
Minutes without an active partnership before fallback suspends itself. 0 suspends immediately.
minutes
Tier 2 delay
How long this host must be dark before the partner starts its Tier 2 containers.
minutes
Tier 3 delay
Same for Tier 3 — secondary services that can wait out a short outage.
minutes
Tier 4 delay
Same for Tier 4 — the last to move, usually arrs and downloaders.
minutes
Internet probe target
Pinged to tell "the partner is down" apart from "our own line is down". Must be reachable from both hosts.
'varaverk',
'compact' => true,
// Fallback is the mesh's business by definition — a failover is two hosts agreeing about
// each other — so the mesh side leads here, as it does on Partnership.
'mesh' => true,
'meshDefault' => true,
'title' => 'Assistant',
'height' => '300px',
'tall' => '500px',
'tallLarge' => '750px',
'empty' => 'Ask about fallback — why a tier has not fired, what the partner would '
. 'start if this host went dark, whether a stale state file matters.',
]); ?>