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):
- NO reads/writes are possible across the entire DB?
- Only reads are possible from available shards but no writes are possible to any shard?
- Reads/writes to non-missing shards are possible, but reads/writes to missing shards are not possible?
- 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?