{"push_id":846721782,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d8f3b490bbb691c9916eed0df5b980c1aef23c85","before":"30a6a2247b3d9e177398779544ef0d3e17e2bef7","commits":[{"sha":"d8f3b490bbb691c9916eed0df5b980c1aef23c85","author":{"email":"a505e7c038746dbeb3edcd8d146dbd515432801f@gmail.com","name":"Amitay Isaacs"},"message":"ctdb-banning: Do not set recovery mode to ACTIVE in daemon\n\nWhen a node gets banned, it should go into recovery and freeze all\ndatabases.  We rely on the recovery daemon to detect the banned state\nand put the node in recovery and freeze all databases.\n\nRecent change in b4357a79d916b1f8ade8fa78563fbef0ce670aa9 took explicit\nfreezing out of banning code but left the setting of recovery mode\nto ACTIVE.  Recovery daemon will freeze databases only if the recovery\nmode is NORMAL.  Recovery mode set to ACTIVE is an indication that the\nfreeze has started.\n\nDo not set the recovery mode to ACTIVE in banning.  Let recovery daemon\ntake care of it.\n\nSigned-off-by: Amitay Isaacs <amitay@gmail.com>\nReviewed-by: Martin Schwenke <martin@meltin.net>\n\nAutobuild-User(master): Martin Schwenke <martins@samba.org>\nAutobuild-Date(master): Fri Oct 30 10:32:38 CET 2015 on sn-devel-104","distinct":true,"url":"https://api.github.com/repos/samba-team/samba/commits/d8f3b490bbb691c9916eed0df5b980c1aef23c85"}]}