"[EMAIL PROTECTED]" wrote : "[EMAIL PROTECTED]" wrote : | | | | Ok, then it would be implemented as follows: | | | | 1. TM depends on RecoveryManager | | 2. Recovery manager records prexisting log files. | | 3. Recovery Manager creates new log files. | | 4. Everybody starts up. | | 5. Recover Manager receives START notification. Starts recovering on prexisting recorded file list. | | | | You still have an unrepeatable operation. | |
No you don't. The files are not renamed. If covery fails at any point, then the next server reboot will just retry those log files. anonymous wrote : | It is not a good idea | to dynamically create logs (it might fail - no disk space - at just the wrong time). | The disk might fail, but this does not create a scenario of inconsistent state. Prepared resources will just get rolled back during recovery. anonymous wrote : | Logs should be preallocated space and reused - you rewrite the log(s) from the memory | at checkpoints. | Personally, I prefer a simpler design than a rolling, preallocated log file. I think requiring enough disk space is a reasonable requirement. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860474#3860474 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860474 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
