Changes between Version 71 and Version 72 of FAQ

Timestamp:

2012-04-18T21:54:14Z (12 years ago)

Author:

zooko

Comment:

link to wiki page on server selection

FAQ

@@ -72 +72 @@
 '''[=#Q12_server_location_distribution Q12:] If I had 3 locations each with 5 storage nodes, could I configure the grid to ensure a file is written to each location so that I could handle all servers at a particular location going down?'''
 
-A: Not directly. We have a ticket about that one (#467, #302), but it's deeper than it looks and we haven't come to a conclusion on how to
+A: Not directly. We have [wiki:ServerSelection a wiki page] and some tickets (linked from the wiki page) about this but it's deeper than it looks and we haven't come to a conclusion on how to
 build it.
 
-The current system will try to distribute the shares as widely as possible, using a different pseudo-random permutation for each file, but
-it is completely unaware of server properties like "location". If you have more free servers than shares, it will only put one share on any
-given server, but you might wind up with more shares in one location
-than the others.
+The current system will try to distribute the shares as widely as possible, using a different pseudo-random permutation for each file, but it is completely unaware of server properties like "location". If you have more free servers than shares, it will only put one share on any given server, but you might wind up with more shares in one location than the others.
 
-For example, if you have 15 servers in three locations A:1/2/3/4/5, B:6/7/8/9/10, C:11/12/13/14/15, and use the default {{{3-of-10}}} encoding,
-your worst case is winding up with shares on 1/2/3/4/5/6/7/8/9/10, and not use location C at all. The most *likely* case is that you'll wind up
-with 3 or 4 shares in each location, but there's nothing in the system to enforce that: it's just shuffling all the servers into a ring,
-starting at 0, and assigning shares to servers around and around the ring until all the shares have a home.
+For example, if you have 15 servers in three locations A:1/2/3/4/5, B:6/7/8/9/10, C:11/12/13/14/15, and use the default {{{3-of-10}}} encoding, your worst case is winding up with shares on 1/2/3/4/5/6/7/8/9/10, and not use location C at all. The most *likely* case is that you'll wind up with 3 or 4 shares in each location, but there's nothing in the system to enforce that: it's just shuffling all the servers into a ring, starting at 0, and assigning shares to servers around and around the ring until all the shares have a home.
 
 The possible distributions of shares into locations (A, B, C) are: