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

Michael Adam obnox at samba.org
Wed Sep 4 07:32:48 MDT 2013

The annotated tag, ctdb- has been created
        at  d21459e64283a20978b6a5339d3a6ea8fc29cca7 (tag)
   tagging  052001d83de13c20705c9701bb47c06959096ee7 (commit)
  replaces  ctdb-
 tagged by  Michael Adam
        on  Wed Sep 4 15:31:49 2013 +0200

- Log -----------------------------------------------------------------
Version: GnuPG v1.4.11 (GNU/Linux)


Amitay Isaacs (23):
      vacuuming: Fix vacuuming bug where requests keep bouncing between nodes (part 1)
      vacuuming: Fix vacuuming bug where requests keep bouncing between nodes (part 2)
      vacuum: Reduce the priority of non-critical error
      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

Martin Schwenke (6):
      Added some #ifndefs to stop files being included multiple times.
      Clean up warnings: remove changed_flags in monitor_helper
      recoverd: All inactive nodes should yield recovery master role
      recoverd: Clarify some misleading log messages
      recoverd: main_loop() should not verify local IPs if node is stopped
      recoverd: Don't continue if the current node gets banned

Michael Adam (8):
      Fix the build after backporting f3bf2ab61f8dbbc806ec23a68a87aaedd458e712.
      ctdbd: update comment describing ctdb_call_send_redirect()
      ctdbd: remove a nonempty blank line
      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
      New version

Ronnie Sahlberg (4):
      When memory allocations for recovery fails,
      In the recovery daemon, keep track of which node we have assigned public ip
      The recent change to the recovery daemon to keep track of and
      rename ctdb_set_message_handler to ctdb_client_set_message_handler

Rusty Russell (3):
      idtree: fix right shift of signed ints, crash on large ids on AIX
      idtree: fix overflow for v. large ids on allocation and removal
      speed startup: alter recovery loop

Sumit Bose (6):
      Check return value of tdb_delete()
      Fixes for various issues found by Coverity
      Fix memory leak in ctdb_send_message()
      IPv6 neighbor solicit cleanup
      Print deleted nodes as well
      Set FD_CLOEXEC for epoll file descriptors

Volker Lendecke (1):
      tdb: Fix Coverity ID 2192: NO_EFFECT


CTDB repository

More information about the samba-cvs mailing list