[SCM] CTDB repository - branch 1.0.69 created - 8ae93da7f6341f1cddb15786df67644f29648b9b

[Andrew Tridgell]

The branch, 1.0.69 has been created
        at  8ae93da7f6341f1cddb15786df67644f29648b9b (commit)

- Log -----------------------------------------------------------------
commit 8ae93da7f6341f1cddb15786df67644f29648b9b
Author: Andrew Tridgell <tridge at samba.org>
Date:   Tue May 5 12:17:21 2009 +1000

    fixed an error with newer autotools versions

commit b06d4c6ee7da97aaa810aa4c95952b6505cf720f
Author: Andrew Tridgell <tridge at samba.org>
Date:   Tue May 5 12:17:07 2009 +1000

    fixed a problem with clients disconnecting during a traverse
    
    When a client (such as smbstatus) is killed, it may have outstanding
    traverse children on remote nodes. We need to catch the client
    disconnect in ctdbd and send a control to all nodes telling them to
    kill those outstanding traverse children.

commit d26d522fd0a1df7f06be056e7458ed5349a00658
Author: root <root at rcn1.VSOFS1.COM>
Date:   Tue May 5 10:24:14 2009 +1000

    new version 1.0.69-6

commit d02c0e9371981bc6830f792d65e9f08832656cf0
Author: root <root at rcn1.VSOFS1.COM>
Date:   Tue May 5 09:55:36 2009 +1000

    try to add the routes back also for the releaseip event to workaround the issue
    with when the kernel removes too many addresses (see 10.interfaces for the details)

commit 87e674f93728fb20209b6473f07ca323530ddbdc
Author: root <root at rcn1.VSOFS1.COM>
Date:   Fri May 1 01:24:27 2009 +1000

    new version 1.0.69-5

commit 478f43bc3c970edc7c8db3e34095774261a48056
Author: root <root at rcn1.VSOFS1.COM>
Date:   Fri May 1 01:18:27 2009 +1000

    Add a new variable VerifyRecoveryLock which can be used to disable the test that the recovery daemon holds the lock properly when performing a recovery

commit a63c79318678abe99d2a36fe4465e63eafc008b7
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Sun Apr 26 08:50:35 2009 +1000

     new version 1.0.69-4

commit 8628402d4cad4b9ef580151b85e36b6a5909e56c
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Sun Apr 26 08:47:38 2009 +1000

    we only need to have transaction nesting disabled when we start the new transaction for the recovery

commit c61c4f7a7628232e9094d463275ba6abf7b79941
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Sun Apr 26 08:42:54 2009 +1000

    set the TDB_NO_NESTING flag for the tdb before we start a transaction from within recovery

commit 460e6b2402fc9bca9e9835e3a203278ac0bcaf8f
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Sun Apr 26 08:38:37 2009 +1000

    add TDB_NO_NESTING. When this flag is set tdb will not allow any nested transactions and tdb_transaction_start() will implicitely _cancel() any pending transactions before starting any new ones.

commit fb582515c674b76e06aed28d04f24ae3a849cfe2
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Fri Apr 24 18:23:48 2009 +1000

    add a tuneable RecoveryDropAllIPs  so it is possible to control after how long a node that has been stuck in recovery will wait until it will yield all public addresses.
    
    this now defaults to 60 seconds
    
    This is useful if a split brain occurs due to network partitioning since it will make sure that the "other half" of the cluster that does not contain the recovery master will eventually release all ips and thus avoiding a duplicate ip situation for the public addresses

commit b5ef99f14fb02deb128b4b0956508fc980886407
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Fri Apr 24 18:09:51 2009 +1000

    increase the loglevel for the message we print when we automatically release all ips when we have been in recovery for too long

commit ac5557659e667da5f3a33cc612e06a21396fce2d
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Fri Apr 24 14:43:48 2009 +1000

    new version 1.0.69-3

commit 968739ea9af2aaba90e6bb4569ae4d9fb60b79aa
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Fri Apr 24 14:41:21 2009 +1000

    tweak some timeouts so that we do trigger a banning even if the control hangs/timesout

commit 2031fd8b83bd832d1104128c3faddf209e6bb23e
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Fri Apr 24 13:58:32 2009 +1000

    If we can not pull a database from a node during recovery, mark this node as a "culprit" so that it will eventually become banned.

commit 0563b3c6d9787164475538fbc1342f8c6be62eac
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Thu Apr 23 09:31:44 2009 +1000

    new version 1.0.69-2

commit 3aba067b7fa7d77836901f82deee441a07b3a15d
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Mon Apr 6 12:00:22 2009 +1000

    We dont need to verify the nodemap on remote nodes that are banned

commit 0a7dbe56d1b4545e9f45c29ea719d24b3b3ada3e
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Thu Apr 2 14:50:43 2009 +1100

    if we cant pull the remote nodemap off a node we should mark it as a culprit so it eventually becomes banned.

commit 767e92f64b63a6bcaa36efe633e8a3e55a803e79
Author: root <root at test1n1.VSOFS1.COM>
Date:   Thu Feb 5 12:56:22 2009 +1100

    New version 1.0.69_1

commit 7b6bada79b4e0534b261440438b4256bc446191f
Author: root <root at test1n1.VSOFS1.COM>
Date:   Thu Feb 5 12:18:17 2009 +1100

    dont return error if update nodeflags failed.   this can happen when we talk
    to older ctdb versions

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


-- 
CTDB repository