Behavior when all replicas of some shards are missing?

I wanted to check what is the expected behavior of FDB when all replicas of some of the shards are missing (due to some of SS nodes being unavailable):

  1. NO reads/writes are possible across the entire DB?
  2. Only reads are possible from available shards but no writes are possible to any shard?
  3. Reads/writes to non-missing shards are possible, but reads/writes to missing shards are not possible?
  4. Reads for keys on missing shard will be treated as if those keys were unset and therefore return ‘null’ kv row without any exception?

How would shard splitting and merging work under such a situation - given that some shards are not available, how will any shard merge/split work that wants to touch a part of key range associated with missing shards?

Would there be any other aspects of FDB that will not function till such a situation continues?

Is there a setting to automatically make the entire database “un-available” (no reads and no writes) till there is at least one replica available for each of the shard?

I finally looked at my todo list to ask Evan about this while Evan was still sitting behind me, as both AJ and I were not entirely certain without doing a good amount of testing/code reading.

The answer for reads and writes is 3.5: Reads and writes to non-missing shards will continue as normal. Writes to missing shards will be possible, but will buffer indefinitely on TLogs, potentially eventually filling up their disk space. Reads from missing shards will hang indefinitely.

We believe that data distribution will probably get stuck on some of the servers, so it’s likely that splitting and merging for servers that shared a team with the now-missing shard will have trouble adapting to new load. Ratekeeper should continue as is, as it only monitors things that are alive.

I’m not aware of any knob or client setting that currently exists that would make FDB act as unavailable until one replica of each shard is present.