Client Writer State

In order to maintain continuity across writer restarts, writers will need to maintain state across restarts. The state at a minimum requires the hash of the last written record, although other information may be required.


Not started.


Different client hardware is likely to have different options for long term state. In the short run a disk file is probably sufficient, but some systems may require the use of eeprom or similar technologies.

Committing state to persistent storage on each append is probably too expensive for some applications. There may be a need to implement these as periodic checkpoints rather than immediate writes, especially if the data is flushed to the physical storage.