kvs: add root sequence number to checkpoint object #4446
Assignees
Comments
This was referenced Jul 29, 2022
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Aug 8, 2022
Problem: The KVS root sequence number isn't persisted across restarts. It restarts at zero everytime the KVS module is loaded. Solution: Add the root sequence number to the checkpoint object, read it in and initialize the KVS primary namespace to that sequence number. Fixes flux-framework#4446
jameshcorbett
pushed a commit
to chu11/flux-core
that referenced
this issue
Aug 8, 2022
Problem: The KVS root sequence number isn't persisted across restarts. It restarts at zero everytime the KVS module is loaded. Solution: Add the root sequence number to the checkpoint object, read it in and initialize the KVS primary namespace to that sequence number. Fixes flux-framework#4446
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem: the KVS root sequence number, mentioned in #4311 as an indicator of how much change has been committed to the kvs, isn't persistent across restarts (e.g. it's not stored with the root hash in the checkpoint object). It therefore isn't a great indicator since it resets to zero whenever the instance restarts, whether a GC dump occurs across that reset or not.
Add the root sequence number to the checkpoint object. It should not be necessary to bump the checkpoint object version. We can just tolerate a missing sequence number when parsing and have it read as zero.
The text was updated successfully, but these errors were encountered: