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

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

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

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

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

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

Hiding exceptions is *bad* .

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

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

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

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

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

This condition is always true as the primary_node was found by UUID.

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

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

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

This fixes strange epoll results (yielding unknown file descriptors).
There is no explanation as of why it worked in 64bits until now.

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

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

Consequence of previous commit, to preserve code clarity.

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

This state was only internal to master node, and was not even
consistently handled in master (only the first election was done in that
state).
changeClusterState was never called with that state as parameter.
Finally, remove this state from protocol as it's not used any longer.

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