Commit b35080bc authored by Vincent Pelletier's avatar Vincent Pelletier

Update TODO on pack: implemented, but too aggressive and incomplete.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2331 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 14afe2bb
...@@ -62,7 +62,11 @@ RC - Review output of pylint (CODE) ...@@ -62,7 +62,11 @@ RC - Review output of pylint (CODE)
connection is thread-safe (MT version of connection classes). connection is thread-safe (MT version of connection classes).
Also, the code to detect wether a response is expected or not must be Also, the code to detect wether a response is expected or not must be
genericised and moved out of handlers. genericised and moved out of handlers.
- Pack (FEATURE) - Implement transaction garbage collection API (FEATURE)
NEO packing implementation does not update transaction metadata when
deleting object revisions. This inconsistency must be made possible to
clean up from a client application, much in the same way garbage
collection part of packing is done.
- Factorise node initialisation for admin, client and storage (CODE) - Factorise node initialisation for admin, client and storage (CODE)
The same code to ask/receive node list and partition table exists in too The same code to ask/receive node list and partition table exists in too
many places. many places.
...@@ -138,6 +142,12 @@ RC - Review output of pylint (CODE) ...@@ -138,6 +142,12 @@ RC - Review output of pylint (CODE)
In its current implementation, replication runs at full speed, which In its current implementation, replication runs at full speed, which
degrades performance for client nodes. Replication should allow degrades performance for client nodes. Replication should allow
throttling, and that throttling should be configurable. throttling, and that throttling should be configurable.
- Pack segmentation & throttling (HIGH AVAILABILITY)
In its current implementation, pack runs in one call on all storage nodes
at the same time, which lcoks down the whole cluster. This task should
be split in chunks and processed in "background" on storage nodes.
Packing throttling should probably be at the lowest possible priority
(below interactive use and below replication).
Master Master
- Master node data redundancy (HIGH AVAILABILITY) - Master node data redundancy (HIGH AVAILABILITY)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment