| | 1 | Redis TODO |
| | 2 | ---------- |
| | 3 | |
| | 4 | WARNING: are you a possible Redis contributor? |
| | 5 | Before implementing what is listed in this file |
| | 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 |
| | 11 | |
| | 12 | |
| | 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 | |
| | 24 | SCRIPTING |
| | 25 | ========= |
| | 26 | |
| | 27 | * SCRIPT FLUSH or alike to start a fresh interpreter? |
| | 28 | |
| | 29 | OPTIMIZATIONS |
| | 30 | ============= |
| | 31 | |
| | 32 | * SORT: Don't copy the list into a vector when BY argument is constant. |
| | 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. |
| | 34 | * Read-only mode for slaves. |
| | 35 | * Redis big lists as linked lists of small ziplists? |
| | 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. |
| | 37 | |
| | 38 | KNOWN BUGS |
| | 39 | ========== |
| | 40 | |
| | 41 | * #519: Slave may have expired keys that were never read in the master (so a DEL |
| | 42 | is not sent in the replication channel) but are already expired since |
| | 43 | a lot of time. Maybe after a given delay that is undoubtably greater than |
| | 44 | the replication link latency we should expire this key on the slave on |
| | 45 | access? |
projects / redis.git / blame_incremental