Hi all,
As you may know, the recovery log is now a mandatory component in Sequoia 3.
For those who don't want to bother with tweaking the recovery log
configuration, the upcoming Sequoia 3.0beta2 includes an
EmbeddedRecoveryLog element that requires no configuration.
The Sequoia demos are now using this new recovery log implementation
that is based on a fast embedded HSQLDB. To use it, just include the
following in your configuration file:
...
</LoadBalancer>
<EmbeddedRecoveryLog/>
</RequestManager>
By default, the recovery log data files will be in
$SEQUOIA_HOME/recoverylog/vdbName. If you want to store the log in a
separate path, you can use the dataPath attribute to force another path.
Example: <EmbeddedRecoveryLog
dataPath="../recoverylog/controller1/myDB/recoverylog"/>
Note that in terms of performance, this does not require network or
inter-process communication for recovery log updates which makes it
probably one of the fastest approach to implement a recovery log.
Keep us posted if you have any trouble using this option (currently
available in CVS HEAD and soon in 3.0beta2).
Thanks in advance for your feedback,
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
