[redis.git] / TODO

Redis TODO
----------

WARNING: are you a possible Redis contributor?
         Before implementing what is listed in this file
         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


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?).

SCRIPTING
=========

* SCRIPT FLUSH or alike to start a fresh interpreter?

OPTIMIZATIONS
=============

* 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.
* Read-only mode for slaves.
* 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.

KNOWN BUGS
==========

* #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 undoubtably greater than
  the replication link latency we should expire this key on the slave on
  access?
Commit	Line	Data
4c22fd34	1	Redis TODO
4c22fd34	2	----------
f284d963	3
4c22fd34	4	WARNING: are you a possible Redis contributor?
5833cf16	5	Before implementing what is listed in this file
4c22fd34	6	please drop a message in the Redis google group or chat with
	7	antirez or pietern on irc.freenode.org #redis to check if the work
	8	is already in progress and if the feature is still interesting for
	9	us, and how exactly this can be implemented to have good changes
	10	of a merge. Otherwise it is probably wasted work! Thank you
f6b141c5	11
bb8716b6	12
8905378c	13	CLUSTER
	14	=======
	15
	16	* Implement rehashing and cluster check in redis-trib.
	17	* Reimplement MIGRATE / RESTORE to use just in memory buffers (no disk at
	18	all). This will require touching a lot of the RDB stuff around, but we may
	19	hand with faster persistence for RDB.
	20	* Implement the slave nodes semantics and election.
	21	* Allow redis-trib to create a cluster-wide snapshot (using SYNC).
	22	* Allow redis-trib to restore a cluster-wide snapshot (implement UPLOAD?).
	23
70ecddc9	24	SCRIPTING
	25	=========
	26
70ecddc9	27	* SCRIPT FLUSH or alike to start a fresh interpreter?
70ecddc9	28
4c22fd34	29	OPTIMIZATIONS
4c22fd34	30	=============
0188805d	31
682ac724	32	* SORT: Don't copy the list into a vector when BY argument is constant.
682ac724	33	* 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.
4c22fd34	34	* Read-only mode for slaves.
e9ee513b	35	* Redis big lists as linked lists of small ziplists?
e9ee513b	36	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.
cef34df0	37
	38	KNOWN BUGS
	39	==========
	40
8231b1ef	41	* #519: Slave may have expired keys that were never read in the master (so a DEL
8231b1ef	42	is not sent in the replication channel) but are already expired since
5215ab14	43	a lot of time. Maybe after a given delay that is undoubtably greater than
8231b1ef	44	the replication link latency we should expire this key on the slave on
8231b1ef	45	access?