There are at least two bugs in the compaction lifecycle transaction log -
one that can drop an ABORT / ADD in the wrong order (and prevent startup),
and one that allows for invalid timestamps in the log file (and again,
prevent startups).
I believe it's safe to work around the former by removing
Hi all - I replaced a node in a 14 node cluster, and it rebuilt OK. I
started to see a lot of timeout errors, and discovered one of the nodes
had this message constantly repeated:
"waiting to acquire a permit to begin streaming" - so perhaps I hit this
bug:
https://www.mail-archive.com/commits
