[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Journal Cleanup and Journal Compactor

clebert.suconic@jboss.com do-not-reply at jboss.com
Thu Jun 11 12:26:21 EDT 2009


No.. I don' t want to write a database :-)

Instead of using external files to control the compacting, I suggest we do it using the current transaction support we already have on the journal.

One way of doing it would be to create a MOVE operation that would delete it on its original file, and re-add it on the current used file. That operation could be done inside a journal-transactional, so we would have all the control of crashes for free on that operation.

On my previous post I was thinking about changing the internal ID of the record when moving it, but I could do it without changing it.

You might say we would have an issue with Ordering... but compacting the way you said would be the same thing.. since the file would get a new ID and be on the top of the list. But compacting could give you the same issue since the new file receiving the compacting would get a newID.

Maybe sort by ID would fix the issue?


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237083#4237083

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237083



More information about the jboss-dev-forums mailing list