Tranlog full with STN_COMMITS_ASYNC may result in lost record
With STN_COMMITS_ASYNC, if the tranlogs become full and the Stone has to wait for more space to become available, the tranlog record that was waiting to be may not actually get written, depending on the particular point in which the tranlog directories full conditions are encountered.
A later replay of the transaction logs may encounter errors, depending on the nature of the lost record, and be unusable.
Workaround
Ensure that STN_COMMITS_ASYNC is set to false; this is enforced with v3.5 and 3.4.4.
It is always strongly recommended to avoid tranlog full conditions.
Last updated: 8/6/19