INFO now contains the time (in usecs) needed to fork() in order to persist. The info...

[redis.git] / TODO

diff --git a/TODO b/TODO
index 92b6ea9304d1c36d5ec47b27b8f7e0f1eb3ad581..dd6ba28bd6f149b7644849833df8b6a02f759fb7 100644 (file)
--- a/TODO
+++ b/TODO
@@ -17,6 +17,17 @@ API CHANGES
   the variable number of arguments represent values, and there is no conflict
   with the return value of the command.
 
   the variable number of arguments represent values, and there is no conflict
   with the return value of the command.
 

+CLUSTER
+=======
+
+* Implement rehashing and cluster check in redis-trib.
+* Reimplement MIGRATE / RESTORE to use just in memory buffers (no disk at
+  all). This will require touching a lot of the RDB stuff around, but we may
+  hand with faster persistence for RDB.
+* Implement the slave nodes semantics and election.
+* Allow redis-trib to create a cluster-wide snapshot (using SYNC).
+* Allow redis-trib to restore a cluster-wide snapshot (implement UPLOAD?).
+

 APPEND ONLY FILE
 ================
 
 APPEND ONLY FILE
 ================
 


@@ -54,6 +65,11 @@ KNOWN BUGS
     What happens if between 1 and 2 for some reason (system under huge load
     or alike) too many time passes? We should prevent expires while the
     AOF is loading.
     What happens if between 1 and 2 for some reason (system under huge load
     or alike) too many time passes? We should prevent expires while the
     AOF is loading.

+* #519: Slave may have expired keys that were never read in the master (so a DEL
+  is not sent in the replication channel) but are already expired since
+  a lot of time. Maybe after a given delay that is undoubltly greater than
+  the replication link latency we should expire this key on the slave on
+  access?

 
 DISKSTORE TODO
 ==============
 
 DISKSTORE TODO
 ==============