Hi folks-
As many of you know, when running Brooklyn if rebind fails the server
responds safety-first by failing or declining to start. You then trawl
through the logs, investigate the persisted state, resolve the issues,
and restart it. Ideally this would be visible and resolvable within the
server itself. To this end I'm thinking of:
* a new "maintenance mode" that the server would run in if there are
problems in startup or failover
* when in maintenance mode (or even HA standby mode), you are presented
with a warning in the GUI but you can set an http session flag to allow
access (if you have the entitlement)
* a new "server" tab where server-level tasks are tracked (and other
server operations such as shutdown, force failover, etc, could be
sensibly re-housed)
* all startup activities and HA activities are run as server-level tasks
and visible in the server tab (which would allow you to see the reason
for HA failures)
* HA state could be edited in the server tab, when a server is in
maintenance mode, to resolve problems and drive rebind
Is this a good evolution?
Best
Alex
