GitLab

The lease commands are to be timestamped by the server, not
the client. Let's just pretend to sneaky clients that
timestamped lease commands simply do not exist.

Error messages etc are a bit rough right now, we need to
refactor a few things as well, and add more tests. But the
basic functionality works.

And add a comment detailing what's going on.

This is a valid case: The raft term changes after retrieving
the state snapshot, but before inserting into the journal.

The journal correctly rejects the entry - we should simply
warn and report "unavailable" to the client.

Stalling writers until the leadership marker has been applied
makes this race far more common - stress tests were failing,
but the race itself was there even before.

Just because we can. :P An automated client should never need to
call this.

Along with some more information: last renewal time, and deadline.

Ordered by deadline.

DEL would iterate over the contents of the DB,
not the contents of the staging area. (pending
changes + DB)

A transaction with the following commands was
able to trip an assert and cause a crash:

- HSET hash f1 v1
- HSET hash f2 v2
- DEL hash

Since DEL was only able to scan fewer elements than
the size of the key descriptor (due to not having
"hash#f1" and "hash#f2" in the main DB yet), it
would detect something was wrong and assert.

Has never happened so far, but it's only a matter
of time.

To be used with leases.

Most key + fields will end up being larger than 32 bytes.
Increasing this a bit will save lots of dynamic allocations.

Most will be a single line - this makes them easily
copy-pasteable without having to worry about newlines.

Gives cleaner output in MONITOR.