"timfox" wrote : Can't completions come in for a previous file once we've already moved to the next file? Yes... When the journal needs a new file it will: - Immediately return the next file (cached). Writes will start on the next file without any waits. In an executor: A- It will wait the pending writes to finish before it can close the file, and then close the file (This won't affect any of the transactions. It's just that I need to wait executions to finish before I can close the file or I would loose data) B- It will place another file back to the nextOpenFile cache. I have tested this and I didn't see any latency because of that. BTW: (A) is being tested under one of the integration tests, as this used to cause a crash on the native layer before Alpha. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173332#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...