Page History

...

1. Cluster info
   1. We must add some property to allow user to configure which DC node belongs to.
   2. This property must included in node info known cluster-wide. 
2. Discovery SPI
   1. TcpDiscovery must minify cross DC communication by forming discovery ring with only two cross DC edges.

   2. ZooKeeperDiscovery  has it's own guarantees related to ZK cluster. 

3. Affinity
   1. We must allow to the user to setup two different Affinities:
      1. multi DC - when cache partitions must be spread to as many DC as possible to overcome DC outages.
      2. Do we need to support "single DC" configuation? Do we have real-world use-cases for it?
4. Queries
   1. FULL_SYNC and readFromBackupt=true is a primary setup here. 
   2. Key-value API must go to the same DC nodes whenever possible.
      1. From the first glance, looks like it's possible to read always from 
   3. SQL - calcite engine must maps queries fragments to the same DC nodes whenever possible.
5. Client nodes
   1. Must connect to the same DC server nodes.
6. Thin clients
   1. Must support same DC read key-value queries.
   2. Must select same DC server node for a node-binded communcations: transactions, tasks, etc
7. Rebalance
   1. Partitions must be loaded from same DC nodes whenever possible.
8. Snapshot restoration
   1. When restore on different topology must load partitions from same DC nodes whenever possible.
9. Configuration
   1. network, query, transaction and other timeouts must be set with respect to cross dc latency.
10. Topology validator
11. Reed solomon codes to reduce replication factor support 
12. Testing
    
    1. Standard setup - 3 dc + 5 backups? must be carefully tested.