Redis test ports selection made more robust. This prevents the test from hanging...

[redis.git] / CLUSTER

diff --git a/CLUSTER b/CLUSTER
index 0e836cb126d3292be6bdded041d97f09732110bf..f8c2daf98779a63ff342b645ea26231798879eb3 100644 (file)
--- a/CLUSTER
+++ b/CLUSTER
@@ -1,6 +1,27 @@
+CLUSTER README
+==============
+
+Redis Cluster is currently a work in progress, however there are a few things
+that you can do already with it to see how it works.
+
+The following guide show you how to setup a three nodes cluster and issue some
+basic command against it.
+
+... WORK IN PROGRESS ...
+
+1) Show MIGRATE
+2) Show CLUSTER MEET
+3) Show link status detection with CLUSTER NODES
+4) Show how to add slots with CLUSTER ADDSLOTS
+5) Show redirection
+6) Show cluster down
+
+... WORK IN PROGRESS ...
+
 TODO
+====
 
-*** WARNING: all the following problably has some meaning only for
+*** WARNING: all the following probably has some meaning only for
 *** me (antirez), most info are not updated, so please consider this file
 *** as a private TODO list / brainstorming.
 
@@ -51,7 +72,7 @@ With -MOVED the client should update its hash slots table to reflect the fact th
        alive table if the received alive timestamp is more recent the
        one present in the node local table.
 
-       In the ping packet every node "gossip" information is somethig like
+       In the ping packet every node "gossip" information is something like
        this:
 
        <ip>:<port>:<status>:<pingsent_timestamp>:<pongreceived_timestamp>