git-svn-id: https://svn.erp5.org/repos/neo/trunk@1492 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1491 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1490 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1489 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1488 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1487 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1486 71dcc9de-d417-0410-9af5-da40c76e7ee4

NotifyTransactionFinished is misspelled, it is an answer packet.
Similary, UnlockInformation is a notification, not a request.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1485 71dcc9de-d417-0410-9af5-da40c76e7ee4

There is no need to store the master address list out of the node manager, any master found in configuration is loaded in the node manager and can be retreived by it if needed.
Remove redundant intialization code in test module, master nodes are created at app initialization.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1484 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1483 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1482 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1481 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1480 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1479 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1478 71dcc9de-d417-0410-9af5-da40c76e7ee4

A storage must never send this packet to the master node. The master has a view of all nodes and detect itself any breakage.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1477 71dcc9de-d417-0410-9af5-da40c76e7ee4

Fit better with the implementation, when a node is identified to the master, it got an entry in the node manager.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1476 71dcc9de-d417-0410-9af5-da40c76e7ee4

This behaviour was probably lost with the master's handler split and was found by fixing unit tests.
During recovery, if a node is lost it's state is updated but not propagated to other (storages) nodes because after the recovery they will all retreive the whole node list.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1475 71dcc9de-d417-0410-9af5-da40c76e7ee4

Send an error to the storage node if the partition table sent is invalid instead of killing the master.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1474 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1473 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1472 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1471 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1470 71dcc9de-d417-0410-9af5-da40c76e7ee4

KeyError may be raised from many statements here, the try/except give no indications.
Also reduce block indentation for readability and add some comments.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1469 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1468 71dcc9de-d417-0410-9af5-da40c76e7ee4

This packet replace notifyPartitionChange when used by storage's replicator at the end of a single partition replication.
In those case, only one partition was involved and the node concerned must match with the sender identify, causing many useless on the master side.
This packet contains only the partition number that is replicated and implies that the node's cell is now up to date.
It should be sent only by the storage node from replicator and received by master node.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1467 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1466 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1465 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1464 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1463 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1462 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1461 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1460 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1459 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1458 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1457 71dcc9de-d417-0410-9af5-da40c76e7ee4

- testUtil module is now empty, but kept for futur tests.
- NeoTestBase got a new getNextTID() method with a copy/paste from master's transactions manager to generate TIDs.
- testProtocol module no more import getNextTID() from neo.util module
- testTransactions test module is updated to test new features provides by transactions manager.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1456 71dcc9de-d417-0410-9af5-da40c76e7ee4

Instead of let the ltid in the master app module, the transaction manager keep it and compute the next each time a transaction begins.
The getNextTID() method has moved from util to transactions module.
Last TID collected during recovery is also handled by the transaction manager through setLastTID() method.
Any reference to app.ltid are updated,

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1455 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1454 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1453 71dcc9de-d417-0410-9af5-da40c76e7ee4