Hi Niraj,
I understand why the recovery log should be mandatory but it would be
great to allow it to be turned off. Not having it has proved to be
useful when I wanted to easily test different configurations.
In fact the logic in the controller does not really make sense without a
recovery log.
If we allow the recovery log to be an optional element, that forces us
to clutter the code with 'if (recoveryLog!=null)' all over the places.
This often leads to NPE in the cases we missed and that adds more
configurations to test in the test suite whereas not having a recovery
log does not allow to add new nodes or recovery from failures (which is
really what Sequoia has been designed for).
If the concern is that users not specifying recovery logs leads to a
greater number of support requests, one option could be to only
support disabling it with source modifications. For example, I believe
that with the current CVS code, things will still work if I manually
modify the vdb DTD to not require the recovery log.
In the 3.0 branch, that should not work and you will certainly end-up
with NullPointerExceptions because the code now assumes the presence of
a recovery log. Note that we could simplify the recovery log definition
by having a default config using an embedded Derby or HSQLDB to store
the log.
What do you think?
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
