------------------------------------------------------------
revno: 207
revision-id: [EMAIL PROTECTED]
parent: [EMAIL PROTECTED]
parent: [EMAIL PROTECTED]
committer: Andrew Tridgell <[EMAIL PROTECTED]>
branch nick: tridge
timestamp: Sat 2007-04-28 09:54:45 +0200
message:
merge from ronnie
modified:
common/ctdb.c ctdb.c-20061127094323-t50f58d65iaao5of-2
common/ctdb_call.c ctdb_call.c-20061128065342-to93h6eejj5kon81-1
common/ctdb_client.c ctdb_client.c-20070411010216-3kd8v37k61steeya-1
common/ctdb_control.c
ctdb_control.c-20070426122724-j6gkpiofhbwdin63-1
common/ctdb_daemon.c ctdb_daemon.c-20070409200331-3el1kqgdb9m4ib0g-1
common/ctdb_message.c
ctdb_message.c-20070208224107-9dnio7x7z33prrmt-1
direct/ctdbd_test.c ctdbd_test.c-20070411085057-17kgjzfktsh28g99-1
include/ctdb_private.h
ctdb_private.h-20061117234101-o3qt14umlg9en8z0-13
------------------------------------------------------------
revno: 197.1.10
merged: [EMAIL PROTECTED]
parent: [EMAIL PROTECTED]
committer: Ronnie Sahlberg <[EMAIL PROTECTED]>
branch nick: ctdb
timestamp: Sat 2007-04-28 01:48:31 +1000
message:
ctdb will now verify that the generation id for all CTDB_REQ_CALLs that
it receives from remote nodes with its own generation number.
if the generation id do not match the daemon will just discard the
packet completely.
this will require that clients such as samba3 will have to be aware that
calls it sends to remote nodes may get lost and will have to resend the
requests after a timeout.
during cluster recovery/reconfiguration the generation nnumbers will be
changing and this can be used to prevent nodes that are still in the
"old" instance from talking to nodes that belong to the new generation
instance
------------------------------------------------------------
revno: 197.1.9
merged: [EMAIL PROTECTED]
parent: [EMAIL PROTECTED]
committer: Ronnie Sahlberg <[EMAIL PROTECTED]>
branch nick: ctdb
timestamp: Sat 2007-04-28 01:19:40 +1000
message:
clients should not fill in "generation" nor be aware of what generation
the cluster is currently in.
remove all instances where the clients try to fill in the generation
field of the header
------------------------------------------------------------
revno: 197.1.8
merged: [EMAIL PROTECTED]
parent: [EMAIL PROTECTED]
committer: Ronnie Sahlberg <[EMAIL PROTECTED]>
branch nick: ctdb
timestamp: Sat 2007-04-28 01:06:26 +1000
message:
add a generation field to the pdu header.
this will allow a node to verify that a received pdu is sent from a node
in the same generation instance of a cluster.
Diff too large for email (214, the limit is 200).
