Commit 86705c29 authored by Grégory Wisniewski's avatar Grégory Wisniewski

Remove an XXX and add a TODO entry for this issue.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1083 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 2d1f4090
...@@ -51,6 +51,11 @@ RC - Review output of pylint (CODE) ...@@ -51,6 +51,11 @@ RC - Review output of pylint (CODE)
- 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 many places. The same code to ask/receive node list and partition table exists in too many places.
- Clarify handler methods to call when a connection is accepted from a listening conenction and when remote node is identified (cf. neo/bootstrap.py). - Clarify handler methods to call when a connection is accepted from a listening conenction and when remote node is identified (cf. neo/bootstrap.py).
- Choose how to handle a storage integrity verification when it comes back.
Do the replication process, the verification stage, with or without
unfinished transactions, cells have to set as outdated, if yes, should the
partition table changes be broadcasted ?
Storage Storage
- Implement incremental storage verification (BANDWITH) - Implement incremental storage verification (BANDWITH)
......
...@@ -35,10 +35,6 @@ class StorageServiceHandler(BaseServiceHandler): ...@@ -35,10 +35,6 @@ class StorageServiceHandler(BaseServiceHandler):
conn.notify(protocol.startOperation()) conn.notify(protocol.startOperation())
def _nodeLost(self, conn, node): def _nodeLost(self, conn, node):
# XXX: here the cells are outdated to trigger the replication process
# when the node will come back. It might be better to reduce network
# overload since others nodes known that it's temporarily down and thus,
# outdate by themselves its cells.
logging.info('storage node lost') logging.info('storage node lost')
if not self.app.pt.operational(): if not self.app.pt.operational():
raise OperationFailure, 'cannot continue operation' raise OperationFailure, 'cannot continue operation'
......
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