2010-12-20 12:13:46 +00:00
|
|
|
Redis TODO
|
|
|
|
|
----------
|
2009-11-24 12:47:26 +00:00
|
|
|
|
2010-12-20 12:13:46 +00:00
|
|
|
WARNING: are you a possible Redis contributor?
|
2011-09-21 17:13:43 +00:00
|
|
|
Before implementing what is listed in this file
|
2010-12-20 12:13:46 +00:00
|
|
|
please drop a message in the Redis google group or chat with
|
|
|
|
|
antirez or pietern on irc.freenode.org #redis to check if the work
|
|
|
|
|
is already in progress and if the feature is still interesting for
|
|
|
|
|
us, and *how* exactly this can be implemented to have good changes
|
|
|
|
|
of a merge. Otherwise it is probably wasted work! Thank you
|
2009-10-16 11:44:25 +00:00
|
|
|
|
2010-07-01 12:52:01 +00:00
|
|
|
|
2011-05-06 14:23:14 +00:00
|
|
|
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?).
|
|
|
|
|
|
2011-07-13 10:04:02 +00:00
|
|
|
SCRIPTING
|
|
|
|
|
=========
|
|
|
|
|
|
|
|
|
|
* SCRIPT FLUSH or alike to start a fresh interpreter?
|
|
|
|
|
|
2010-12-20 12:13:46 +00:00
|
|
|
OPTIMIZATIONS
|
|
|
|
|
=============
|
2009-11-29 11:09:31 +00:00
|
|
|
|
2009-12-05 12:50:36 +00:00
|
|
|
* SORT: Don't copy the list into a vector when BY argument is constant.
|
|
|
|
|
* Write the hash table size of every db in the dump, so that Redis can resize the hash table just one time when loading a big DB.
|
2010-12-20 12:13:46 +00:00
|
|
|
* Read-only mode for slaves.
|
2011-04-11 19:47:45 +00:00
|
|
|
* Redis big lists as linked lists of small ziplists?
|
|
|
|
|
Possibly a simple heuristic that join near nodes when some node gets smaller than the low_level, and split it into two if gets bigger than high_level.
|
2010-05-25 18:28:22 +00:00
|
|
|
|
|
|
|
|
KNOWN BUGS
|
|
|
|
|
==========
|
|
|
|
|
|
2011-04-13 13:39:43 +00:00
|
|
|
* #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
|
2011-07-26 03:18:36 +00:00
|
|
|
a lot of time. Maybe after a given delay that is undoubtably greater than
|
2011-04-13 13:39:43 +00:00
|
|
|
the replication link latency we should expire this key on the slave on
|
|
|
|
|
access?
|
