Guillaume Smet wrote:
Mmmh, IMHO, it's a real problem that you are able to enable the
backend with a failed recovery log. There's something to be done here.
A crashed recovery log should be detected to cause a controller
failure and you shouldn't be able to enable the failed backend without
at least restoring the recovery log.
Do you have any warning in your log file to tell you that the recovery
log is not accessible?
Emmanuel, is it the expected behavior?
Usually a bad recovery log is detected at startup but if the recovery
log database couldn't be updated since the last proper start of a
controller and the log still appears clear, the controller might not
detect it upon startup. This is very unlikely though.
Hope this clarifies things a bit,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
