greg/machi
1
0
Fork 0
Code Issues 11 Pull requests 1 Projects Releases Packages Wiki Activity Actions

cluster-of-clusters WIP

Browse source
This commit is contained in:
Scott Lystig Fritchie 2015-06-17 10:48:57 +09:00
parent 796c222dbf
commit a8c914a280
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/cluster-of-clusters/name-game-sketch.org
View file

@ -177,13 +177,13 @@ the head of Cluster2 (which the client magically knows how to
contact), then the result will look something like
~{ok,"foo.s923.z47",ByteOffset}~.
So, ="foo.s923.z47"= is the file name that any Machi CoC client must use
So, ~ "foo.s923.z47" ~ is the file name that any Machi CoC client must use
in order to retrieve the CoolData bytes.
*** Problem #1: We want CoC files to move around automatically
If the CoC client stores two pieces of information, the file name
~"foo.s923.z47"~ and the Cluster ID Cluster2, then what happens when the
~ "foo.s923.z47" ~ and the Cluster ID Cluster2, then what happens when the
cluster-of-clusters system decides to rebalance files across all
machines? The CoC manager may decide to move our file to Cluster66.