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

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

BaseServiceHandler only logic doesn't apply to a client connection, so
there is no benefit in inheriting from it.

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

This makes sure changes made while expecting condition to happen are
visible to that connection.

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

Otherwise, storage shutdown would be handled as an unexpected
disconnection, and would cause the node to reappear as temporarily down.

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

become persistent.

If the storage is stopped before handling partition changed notification,
it will come back with dropped storage node as up-to-date, which is
outside the scope of this test.

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

This makes clear that it is possible to have more than one connection
to/from a given node. Most obvious case is election, where all masters
try to connect with each other.

Deprecate getConnectionByUUID.

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

Ensure all storage nodes started are well known by the master before check that there is no more outdated cells to avoid random false success with no outdated cells but with a missing storage node.

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

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

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

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

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

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

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

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

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

- Replace verification handler (statefull handler)
- Include 'verifyData', 'verifyTransation' and verification related attributes.
- Define 'runManager()' method for future purpose (with other managers).
- Include all 'VerificationFailure' exception related handling.
- Remove support of 'VERIFYING' cluster in 'changeClusterState' as the manager takes precedence.
- Move VerificationException in verification module.

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

To allow latter give an instance instead of a class.

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

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

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

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

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

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

It has no meaning to stay in election state when the primary master is
known. Also, it causes problems as the elected primary master will soon
start sending packets we don't expect while election is running.

handler/election.py:
- Receiving announcePrimary is enough to exit election immediately, so
  reach election end condition (both sets must be empty)
- Receiving answerPrimary with a known primary is enough to exit election
  immediately (don't attempt to connect to to primary master).
app.py:
- Apply PrimaryHandler while iterating over connections when the primary
  master connection is found, rather than once all other connections are
  closed.
- If no primary master connection was found, start establishing one.
handlers/secondary.py:
- Handle connectionCompleted event as we might only reach primary master
  once with this handler if connection was not established during election.
- Likewise, handle connectionFailed event, and treat it as a primary
  failure.
- Stop ignoring answerPrimary packets, instead check that advertised
  primary master is the expected one and request node identification.

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

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

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

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

This makes garbage collector delay logging module deletion upon interpreter
shutdown, preventing occasional tracebacks from epoll thread.

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

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

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

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

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

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

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

This packet was misnamed as it's an answer.

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

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

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

Almost any use of packet was to retreive the msg_id of the request and pass it to answer().
In storage's replicator, critical TIDs are indexed with UUID instead of remote connection ID (full replicator review required).
In admin node, expected answers are still queued with the msg_id but it seems useless as no concurrent queries should happen.

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

The connection now store the last generated remote ID. If no msg_id is supplied to answer(), the last received ID will be used.

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

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