Question about uncommitted transaction in WAL

We are using RocksDB (Java JNI) as cache and working on data replication across multiple nodes.
Can all the transactions be captured in WAL be it committed or uncommitted and read all transactions through getUpdatesSince. Any example or documentation for configuration would be helpful.

As far as I know, Rocksdb does not write to WAL in normal transaction mode before the transaction is committed. The transaction accumulates all the changes and perform them as a one write-batch. If you need to duplicate only the committed transactions it can be done using either a callback of a write or else using a replication of the WAL files . if you need also changes that are part of transaction and are not committed yet than u need to update the write_batch object to support logging of changes …

1 Like