If you are working at CF ONE you are accepting that *any* value for a key+col
combination stored on a replica for a row is a valid response, and that
includes no value.
After the nodes have detected the others are UP they will start their HH in a
staggered fashion, and will rate limit themselve
I'm trying to work through various failure modes to figure out the
proper operating procedure and proper client coding practices. I'm a
little unclear about what happens when a network partition gets
repaired. Take the following scenario:
- cluster with 5 nodes: A thru E; RF = 3; read_cf = 1; writ
