Commit 68de6e7b authored by Grégory Wisniewski's avatar Grégory Wisniewski

Remove TODO entry about object flushing.

Objects no more related to currently assigned partitions are flushed from relationnal database since implementation of PartitionTable.dropPartition() in r1228.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1440 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 0ce9d846
...@@ -132,10 +132,7 @@ RC - Review output of pylint (CODE) ...@@ -132,10 +132,7 @@ RC - Review output of pylint (CODE)
replication should happen independently of cluster state. (Maybe we still replication should happen independently of cluster state. (Maybe we still
need a primary master, to void replicating from an outdated partition need a primary master, to void replicating from an outdated partition
table setup.) table setup.)
- Flush objects from partition cells not served (DISK SPACE) - Flush asynchronously objects from partition cells not served (DISK SPACE)
Currently, when a node stops serving a partition cell, the objects from
that cell are kept in MySQL. They should be removed (possibly
asynchronously, to avoid performance impact).
- Close connections to other storage nodes (SYSTEM RESOURCE USAGE) - Close connections to other storage nodes (SYSTEM RESOURCE USAGE)
When a replication finishes, the connection is not closed currently. It When a replication finishes, the connection is not closed currently. It
should be closed (possibly asynchronously, and possibly by detecting that should be closed (possibly asynchronously, and possibly by detecting that
......
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