samba.git/ctdb/server/ctdb_server.c, branch talloc-2.2.0

ctdb-server: Rename CTDB_BROADCAST_VNNMAP -> CTDB_BROADCAST_ACTIVE

2018-07-02T06:51:22+00:00

This broadcast is misnamed.  Both places where this type of broadcast
is used expect the broadcast to go to all active nodes.

Make the corresponding change to the semantics in the daemon by
sending to all active nodes.

There is a mismatch between the ideas of VNN map and active nodes.  A
node that is not in the VNN map but is active can still host database
records.  These were the same until the LMASTER capability was
introduced and then the logic was not updated.

The only place where the VNN map is relevant is when finding the
location master of a record in the migration code.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=13499

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-daemon: Add code to process ctdb_req_tunnel packets

2017-10-10T09:45:19+00:00

Signed-off-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke

ctdb-daemon: Increase priority of logs for node connect/disconnect

2017-07-04T11:11:16+00:00

Signed-off-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke

ctdb-daemon: Do not allow mixed ctdb versions in a cluster

2017-05-24T15:03:28+00:00

Extend CTDB_REQ_KEEPALIVE packet to include version and uptime.  If CTDB
versions do not match shutdown ctdb.

Signed-off-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke

ctdb-daemon: Drop function ctdb_set_recovery_lock_file()

2016-06-07T22:51:28+00:00

Setting the recovery lock file at startup can be done more simply.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

Revert "ctdb-daemon: Check packet generation against database generation"

2016-02-09T11:39:24+00:00

This reverts commit 0ff90f4fac74e61192aff100b168e38ce0adfabb.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=11707

The checks against database generation are not required since
the global generation is updated as part of updating vnnmap
before the actual database recovery.  This change was done in
5aab31a39a3589b910a78b96071d6aa5e6547696.

Checking only against the database generation is incomplete.  It can
cause CTDB to abort if the following sequence of events happen.

 - CTDB gets REQ_DMASTER packet (gen1)
   This packet processing gets deferred to get a record lock

 - CTDB goes into recovery, marks RECOVERY_ACTIVE
   CTDB recovery helper updates vnnmap (gen2)

 - CTDB processes REQ_DMASTER packet (gen1)
   The check against database generation (gen1) succeeds.
   The check for lmaster is now invalid because VNNMAP has changed.
   This will cause CTDB to abort due to protocol error.

Reverting the patch stops processing packets of older generation before
they get into call processing.

Signed-off-by: Amitay Isaacs 
Signed-off-by: Martin Schwenke 

Autobuild-User(master): Martin Schwenke 
Autobuild-Date(master): Tue Feb  9 12:39:24 CET 2016 on sn-devel-144

ctdb-server: Replace ctdb_logging.h with common/logging.h

2015-11-15T23:46:15+00:00

Signed-off-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke 
Reviewed-by: Michael Adam

Fix various spelling errors

2015-11-06T12:43:45+00:00

Reviewed-by: Andrew Bartlett 
Reviewed-by: Michael Adam 

Autobuild-User(master): Andrew Bartlett 
Autobuild-Date(master): Fri Nov  6 13:43:45 CET 2015 on sn-devel-104

ctdb-daemon: Rename struct ctdb_node_map to ctdb_node_map_old

2015-11-03T23:47:14+00:00

Signed-off-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke

ctdb-daemon: Separate prototypes for common client/server functions

2015-10-30T01:00:27+00:00

This groups function prototypes for common client/server functions in
common/common.h and removes them from ctdb_private.h.

Signed-off-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke