|tlog - Transaction log of Transactor
|This manual page describes the transaction log of transactor, an general purpose transaction coordinator.
|Transactor's transaction log is an eternal log of all transaction data coordinated through transactor.
|Each transaction has a consecutive transaction id (tid), starting with 1 for the first transaction. Each transaction also has a specification id, which is a kind of unique stamp that was handed out to the client (application server) that submitted it to a transactor. The specification id can be used by the client to verify whether the submitted specification was placed in the transaction, or whether another client's request was preferred.
|The transaction log is organized in a hierarchical subdirectory structure under the base directory, with 100 files/directories at most in one directory. To allow for 64 bit transaction id's, there are eight levels of subdirectories between the base directory and the files that contain the transaction data.
|Each file contains 100 transactions. The file is named by the transaction id of the first transaction that it holds. The first file holds a dummy initial transaction with tid 0, since the transaction id value of 0 is not used. A filename is at least four digits long, so that the alphabetic sorting of filenames in the directory is in the right order.
|Each transaction starts with the transaction id, preceded by the letter T, in the first column of a new line. Separated by a blank, the transaction specification id follows; it consists in the letter S, a 16 bit node index, a colon :, and a 64 bit index that is unique to that node, as long as the message logs are not reset.
|Following another blank, the size of the binary transaction data is printed as a text, followed by another blank. Then comes the binary data. All newline characters in the binary data are replaced by a combination of newline and tab, so that continuation lines can be clearly identified by a human viewer. A final newline ends the transaction.
|Currently, old transactions must not be removed from the transaction log. Transactor needs them to find the tid of the last transaction stored in the transaction log.
|The location of the transaction log base directory must be specified as an absolute path in the configuration file.
|transactor(8), transactor.conf(5), transactor_mlog(5)
|Transactor is Copyright 2003, 2004 Claus Fischer
|Transactor was written by Claus Fischer <firstname.lastname@example.org>.