arakoon sometimes corrupts its state when stopped

[vbmithr]

Dec 23 11:16:11 3434: (main|fatal): [rc=42] tlog not properly closed {i=859;v=(Vc ([NOP;],false);m=None;p=31834} 

See that for example. It happens when I launch arakoon, then kill it, then launch it again, etc. I don't know if it is considered a bug or not but it is problematic for me.

[vbmithr]

Well, not sure, but perhaps two instances were running on the same config. I'll investigate and continue posting here.

[domsj]

If you want arakoon to do a clean shutdown you should send it the SIGTERM signal (press Ctrl-C on the terminal with the process or do a kill -15).
The tlog keeps a marker to track if shutdown happened in a clean and expected way.
The reason for this is that tokyo cabinet (which we use as the underlying key-value store) can get corrupted if we don't give it the time it needs to do its thing.. So we added the marker to allows us to know if we can still trust the database.
In case the marker isn't there we recommend removing the node_name.db and truncating and marking the tlog (with the commands ./arakoon.native --truncate-tlog 000.tlog and ./arakoon.native --mark-tlog 000.tlog closed:node_name).
Not sure how documented this is... (sorry about that).

[domsj]

Hmm, just to be clear, when I wrote 000.tlog I meant the last tlog, regardless of which number it has.