Zach Brown e4dca8ddcc Don't shutdown quorum if server startup fails ...

The quorum service shuts down if it sees errors that mean that it can't
do its job.

This is mostly fatal errors gathering resources at startup or runtime IO
errors but it was also shutting down if server startup fails.   That's
not quite right.  This should be treated like the server shutting down
on errors.  Quorum needs to stay around to participate in electing the
next server.

Fence timeouts could trigger this.   A quorum mount could crash, the
next server without a fence script could have a fence request timeout
and shutdown, and now the third remaining server is left to indefinitely
send vote requests into the void.

With this fixed, continuing that example, the quorum service in the
second mount remains to elect the third server with a working fence
script after the second server shuts down after its fence request times
out.

Signed-off-by: Zach Brown <zab@versity.com>

2021-07-30 11:34:52 -07:00

..

exec.sh

scoutfs-tests: initial commit

2019-08-02 16:51:34 -07:00

filter.sh

Don't shutdown quorum if server startup fails

2021-07-30 11:34:52 -07:00

fs.sh

Add fence-and-reclaim test

2021-05-26 14:18:28 -07:00

require.sh

Add t_require_meta_size function

2021-01-26 14:46:07 -08:00