[SCM] CTDB repository - annotated tag ctdb-1.2.65 created - ctdb-1.2.65

[Amitay Isaacs]

The annotated tag, ctdb-1.2.65 has been created
        at  cbc43cae7cc3b7901cc5bf77d4c103ff699d0e88 (tag)
   tagging  dc84c8ed12ed1bf136827b55128c2e74b38bdf55 (commit)
  replaces  ctdb-1.2.64
 tagged by  Amitay Isaacs
        on  Wed Jul 3 10:16:51 2013 +1000

- Log -----------------------------------------------------------------
new version 1.2.65

Amitay Isaacs (22):
      recoverd: When updating flags on nodes, send updated flags and not old flags
      recoverd: Print banning message only after verifying pnn
      freeze: Log message from ctdb_start_freeze() and ctdb_control_freeze()
      freeze: If priority is invalid here, it's time to abort
      freeze: Make ctdb_start_freeze() a void function
      banning: Log ban state changes for other nodes at higher debug level
      recovered: Remove old comment as the code corresponding to that has gone away
      recoverd: Set node_flags information as soon as we get nodemap
      recoverd: Also check if current node is in recovery when it is banned
      banning: Make ctdb_local_node_got_banned() a void function
      banning: No need to check if banned pnn is for local node
      banning: Do not come out of ban if databases are not frozen
      recoverd: Do not set banning credits on a node if current node is inactive
      recoverd: Always do an early exit from main_loop if node is stopped or banned
      recoverd: No need to check if node is recovery master when inactive
      recoverd: Update capabilities only if the current node is active
      recoverd: Delay the initial election if node is started in stopped state
      recoverd: Move code to ban other nodes after we get local node flags
      recoverd: Refactor code to ban misbehaving nodes
      doc: The second half of monitoring is only for recovery master
      ctdbd: Don't ban self if init or shutdown event fails
      New version 1.2.65

Martin Schwenke (3):
      recoverd: Clarify some misleading log messages
      tools/ctdb: Add "force" option to "recover" command
      recoverd: Don't continue if the current node gets banned

Michael Adam (5):
      recoverd: remove bogus comment "qqq" from "add prototype new banning code"
      recoverd: eliminate some trailing spaces from ctdb_election_win()
      recoverd: fix a comment in main_loop
      recoverd: fix a comment typo
      recoverd: when the recmaster is banned, use that information when forcing an election

Stefan Metzmacher (3):
      server/banning: also release all ips if we're banning ourself
      server/recoverd: do takeover_run after verifying the reclock file
      recoverd: try to become the recovery master if we have the capability, but the current master doesn't

-----------------------------------------------------------------------


-- 
CTDB repository