[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Transactional Summary & Holes on the journal

[clebert.suconic@jboss.com]

"timfox" wrote : A problem with that approach is you might have to update the commit record when you compact, since the number of tx operations in the file with the commit might have changed.
  | 

Yes.. I'm already considering that, but this shouldn't be a problem. Just a counter during compacting.


"timfox" wrote : 
  | 
  | The commit record might be in the current file so that will be hard and undesirable.
  | 
  | 

Why that is a problem?

I'm not planning to compact the currentfile in any approach we choose


anonymous wrote : 
  | If you just add update records you don't have to update the actual commit record.
  | 
  | And you have all the information you need to do this - when you compact the journal you know how many tx operations are in the file both before and after, so you can easily add an update record without having to store any extra information in memory.


Actually I don't have any information for this at the moment.

The current implementation throws away the Transaction as soon as the commit/rollback arrives. I only know about the transaction while it is pendingin, during reload and now during compacting.


I would need to add a few collections to support that operation during reclaiming, and also make sure I remove records when the transaction is deleted (if I start making controls of the transaction).

When you consider that at the implementation level it starts getting more complicated.

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

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