mirror of
https://github.com/schoebel/mars
synced 2024-12-16 03:35:03 +00:00
0e6bb47cb6
Originally a trivial silly bug (boolean value was wrong), leading to an endless loop when a local versionlink was missing, which can happen only after a primary crash at the wrong moment shortly after a logrotate (not even during ordinary operations), followed by a hard reboot. As documented in mars-manual.pdf, you simply need "modprobe mars" to recover after such a crash reboot. MARS remembers the primary state persistently for you and restores everything _automatically_. Using "marsadm primary" in such a case to switch the current primary to primary again (after an unnecessary "marsadm secondary" which is strongly discouraged by mars-manual.pdf), although the host is / was already in primary state after the reboot, is at least as silly as the mentioned bug. Doing this in an /etc/init.d/ startup script where it really doesn't belong into, is even more silly. The latter is even an OPERATIONAL RISK, because "marsadm secondary" works _globally_ in the whole cluster (as documented in mars-manual.pdf). Such an improper startup script _can_ (potentially) disturb another cluster member which had become primary in the _meantime_ during reboot. Global cluster operations don't belong into startup scripts, because reboots may happen unintentionally at any time. |
||
|---|---|---|
| .. | ||
| udev | ||
| make-man.sh | ||
| mars-log-impex.c | ||
| marsadm | ||
| marsadm.8 | ||
| write-reboot.c | ||