| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 54377ef8b992f92d3a4ece42ee72e37d22cd2de6)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
parse_nodestring() checks what this used to check. parse_nodestring()
already has the nodemap.
It was a 50-50 decision to decide whether to update verify_node() to
check against a nodemap that is passed in or to delete it.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Conflicts:
tools/ctdb.c
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 2c1baf5ddd3c2cdd2a3f98b8e208d3a48530d1d1)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is very much like "ctdb status" but actually returns the status
for use in scripts.
This can be used in 2 modes:
* An optional nodestring is passed directly to the command without
using -n. In this mode the current node is asked for the status of
all listed nodes.
* The nodestring is passed via -n. In this mode the designated nodes
will be asked for their status. This is like "ctdb status".
These modes can be mixed. For example:
ctdb nodestatus 1,2,3 -n 0
asks node 0 for the status of nodes 1, 2 and 3, returning the bitwise
OR of their statuses.
This version uses the auto_all functionality, so the output isn't
necessarily pretty. An improved version that does its own -n
processing may appear soon.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 355685a14be17bf4648788f8a72c54790fe03502)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Create 2 new functions: control_status_1_machine() and
control_status_1_human() that contain chunks of code from
control_status(). We're about to find another purpose for these
functions.
This should be a no-op.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit fade71539482e8276f57ba3c003fe004d8666ce7)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Centralise -n nodestring parsing and add the ability to pass a
comma-separated list of node numbers. Listing a node that is
disconnected or deleted results in failure, similar to the way passing
a single node currently works. All of the auto_all commands inherit
this functionality. For now, the non-auto_all commands do not inherit
this - they need to be individually tweaked. Therefore, we haven't
updated the documentation to advertise this feature.
Implemented via a new function parse_nodestring() that parses an
optional (pass NULL when not available to indicate "current node")
comma-separated list of node numbers or "all". parse_nodestring() can
be told to be non-fatal for disconnected/deleted nodes so it can also
be used in other contexts (yes, coming soon). main() is changed to
call this function.
A new magic PNN value CTDB_MULTICAST is added and along with a
corresponding option.nodes structure member (a talloc-ed array of
PNNs). This is also populated for "all" as well.
control_status() has new function pretty_print_flags() factored out so
pretty-printed flags can be used in error/debug messages. New
function is_partially_online() is also factored out - this simplifies
some of the logic.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 920e3a732eb9e09004edde6cfb3c7db8a004016f)
|
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 00373958a5d5fb8c9b99548d5b9f327e78669162)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 3f471da605b9c43d5e1206452f238c2a91dc02f7)
|
| |/
| |
| |
| | |
(This used to be ctdb commit 8fc71ad4da746e28406c06a95928052b29803062)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In 8281bb210858ed04992eacea7f6d02261e0fc1b1, I forgot to change
this hunk back when hiding the wire changes done in commit
ddc5da3a0df7701934404192a0a0aa659a806acb behind a new control
CTDB_CONTROL_TRAVERSE_START_EXT.
(This used to be ctdb commit faf25e8a2fdf80a016048e1f698a014ceb5e604f)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 08e06176feab1ec244496e62a916fbb77817239f.
I wanted to fix this differently, not using the extended traverse_start
control...
(This used to be ctdb commit f60de23e0a8307b5baaa9c4b8406b2b223487a48)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This puts the parsing and checking logic close together. This makes
it easy to change the parsing code. Changed parsing code can now
easily use both old client code and libctdb since both are guaranteed
to be setup.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 57fb074a65dc56168fc3813b79a5bab4b3727cf3)
|
| |
| |
| |
| |
| |
| |
| |
| | |
It's the only one in the file.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit bf1174ef699b06485b36ee8ae70412be0759e142)
|
| |
| |
| |
| |
| |
| |
| |
| | |
This allows all that logic to be hacked a little more easily.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit f93ffeee7b9e9ca5dd116655bdc7f89fc987ed8a)
|
| |
| |
| |
| |
| |
| |
| |
| | |
It just doesn't make sense!
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit c4b72683eb046007fbc2e60b4a54bc91faf4cf7e)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Most of the action in main() happens inside a for loop and an if
statement. This causes 2 levels of extra indent for the code and
makes it harder to read.
Instead, the current body of the loop is put below the loop and its
corresponding failure check.
To see how small this change really is, view with "diff -w". ;-)
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 8527396b7290cfc8378779631e91d2ae09e2a106)
|
| |
| |
| |
| | |
(This used to be ctdb commit 0f15a2c65db8f8b4ac0d5ad2755b9aa3c2a8b279)
|
| |
| |
| |
| |
| |
| | |
tool to use this interface
(This used to be ctdb commit 77dc0c7351071243d9096d3607d7499c82f46ec0)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
CTDB has the following limitations on GNU Hurd:
- The pid of a peer is not get from the socket [1]. As a consequence, the peer
process is not killed when releasing IP [2].
- Gratuitous arp are not yet supported [3]
- network interfaces are always considered present [4]
[1]: ctdb_get_peer_pid() in common/system_gnu.c
[2]: release_kill_clients() in server/ctdb_takeover.c
[3]: ctdb_sys_send_arp() in common/system_gnu.c
[4]: ctdb_sys_check_iface_exists() in common/system_gnu.c
(This used to be ctdb commit 00212e5c7dd229e7f8975a165d5ab8875d4917cc)
|
| |
| |
| |
| |
| |
| | |
This removes #ifdef AIX and ease the addition of new platforms.
(This used to be ctdb commit 2fd1067a075fe0e4b2a36d4ea18af139d03f17bf)
|
| |
| |
| |
| |
| |
| |
| | |
server/ctdbd.c: In function ‘main’:
server/ctdb_daemon.c:943:7: warning: zero-length gnu_printf format string [-Wformat-zero-length]
(This used to be ctdb commit e6d1dd3ec4a078e5f32bc52a4a9e4b7d9a2e2d16)
|
| |
| |
| |
| | |
(This used to be ctdb commit 667b174d605646b53f4855e9aaf5f8ce4fdde532)
|
| |
| |
| |
| |
| |
| |
| | |
The traverse control has changed wireformat so update also libctdb to use the correct
version of the wire structure and compile
(This used to be ctdb commit 08e06176feab1ec244496e62a916fbb77817239f)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
control CTDB_CONTROL_TRAVERSE_START_EXT
By this, the original CTDB_CONTROL_TRAVERSE_START control that is
used by e.g. samba's smbstatus, is not changed, so that samba
continues working without code change.
The CTDB_CONTROL_TRAVERSE_START currently just adds the "withemptyrecords"
flag to the state and processon on as CTDB_CONTROL_TRAVERSE_START_EXT.
(This used to be ctdb commit 8281bb210858ed04992eacea7f6d02261e0fc1b1)
|
| |
| |
| |
| | |
(This used to be ctdb commit 6489d0d9b8ec14c7764a1865618faf659800bcc3)
|
| |
| |
| |
| | |
(This used to be ctdb commit 36105b7283df729946e0a2ed61a696a14221efa6)
|
| |
| |
| |
| | |
(This used to be ctdb commit c32604fd0016de0df14845a2f222edaa3c52a4fa)
|
| |
| |
| |
| |
| |
| |
| |
| | |
the list of <srvids>
Specifying the pnn can be done via '-n <pnn>'
(This used to be ctdb commit e9250775f5a1234f27a1a62caa902d7b86194285)
|
| |
| |
| |
| | |
(This used to be ctdb commit 92a391a81d0697956b96e96e39bb1b9d13e18097)
|
| |
| |
| |
| | |
(This used to be ctdb commit ad64ef2c40a2a12b37dbf39142e95c6781c2fc3b)
|
| |
| |
| |
| | |
(This used to be ctdb commit 86d956170d4806065f1470fc44710c085c57f17a)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a new tunable that changes the mode how persistent databases are recovered.
RecoveryPDBBySeqNum
When set to 1, persistent databases will be recovered in whole from the node which
has the highest "__db_sequence_number__" record.
This record is managed by samba for those databases where we do persistent writes and have
inter-record relations.
For these databases we do not want the usual "blend records from all nodes based
on individual record RSN" but instead a mode where we pick one instance of the persistent database.
If no node was found with a "__db_sequence_number__" record at all, we fail back to the original "recover records independently based on record RSN".
Some persistent databases do not contain record interrelations and as such does not
contain this special record at all.
(This used to be ctdb commit 502150c764298a9fa8c4d8aa445bf7d85d4ee9dc)
|
| |
| |
| |
| | |
(This used to be ctdb commit 6e96a62494bbb2c7b0682ebf0c2115dd2f44f7af)
|
| |
| |
| |
| | |
(This used to be ctdb commit 1fea9ef55a6a9d201ad1b49583451ac3e6b1c66d)
|
| |
| |
| |
| | |
(This used to be ctdb commit 3b6ef3442f0b62d65ec0f9be67a2b1dbf7e4af67)
|
| |
| |
| |
| | |
(This used to be ctdb commit 5b527e6127a649fa80dcf9a7599b22bcb7cd3640)
|
| |
| |
| |
| |
| |
| |
| |
| | |
catdb and dumpdbbackup
This changes the default behaviour to not print record flags.
(This used to be ctdb commit 2d2ce07c51055d9400b22cd3c1fd682597cb921c)
|
| |
| |
| |
| | |
(This used to be ctdb commit 0e26774f32d7ea0ce9d034c331730f5324f6b092)
|
| |
| |
| |
| | |
(This used to be ctdb commit 998b7f4450026051867525d91c6d8dcbd2326ab5)
|
| |
| |
| |
| |
| |
| | |
dumping dbs
(This used to be ctdb commit efc033c28ade97f9884794256d59a4553e052d5f)
|
| |
| |
| |
| | |
(This used to be ctdb commit 7f46671fc912c969c5c87e50b77e2e3a7d6c8904)
|
| |
| |
| |
| | |
(This used to be ctdb commit 7e7d86ac9b05f8b67414200adc8ac87cfccf26cf)
|
| |
| |
| |
| |
| |
| | |
catdb"
(This used to be ctdb commit 326f88ef622620cb9e0569c4497bc0e86124beaa)
|
| |
| |
| |
| | |
(This used to be ctdb commit 6f8e7480dadf15d1639355fdb61d5bef025a0325)
|
| |
| |
| |
| | |
(This used to be ctdb commit 9e8045a5b0d8bd9ab2e0343b329de9f45b883531)
|
| |
| |
| |
| |
| |
| |
| |
| | |
dumping data in db dumps
Used in catdb, cattdb and dumpdbbackup.
(This used to be ctdb commit dd866116041e71cbf91e7fd91edcc9501634051d)
|
| |
| |
| |
| | |
(This used to be ctdb commit 079f12dfc1edeac9748af15f652f2f1a6ed35548)
|
| |
| |
| |
| | |
(This used to be ctdb commit 7b4663dd2454b798841815044f898dead9b734e2)
|
| |
| |
| |
| |
| |
| |
| |
| | |
in dumping databases
this option is used with the commands catdb, cattdb and dumpdbbackup.
(This used to be ctdb commit 6ec68a2e667f66d2b194fe48cb75229a2777842e)
|
| |
| |
| |
| |
| |
| | |
empty records.
(This used to be ctdb commit 4ada4bfc4510886c5c7fcf49e09711b9d2dcb75d)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
traverse
This will be useful for also printing information about empty/deleted
records in "ctdb catdb", e.g. for debugging vacuuming issues.
(This used to be ctdb commit ddc5da3a0df7701934404192a0a0aa659a806acb)
|