| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/
| |
| |
| |
| |
| | |
(so one has lots of tiume to play with ctdb_control)
(This used to be ctdb commit 8fbaf82a7b3f0e62c887e91731ad8c659122c785)
|
| |
| |
| |
| |
| |
| | |
node is connected or not
(This used to be ctdb commit 65c5fe53937a17e1fa6de5739cbd01b982dc49bb)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
signature (flags field)
update some calls to ctdb_get_config() to use the new name
ctdb_ctrl_get_config()
change #include "talloc/talloc.h" to #include "lib/talloc/talloc.h" in
lib/events/events.h
(This used to be ctdb commit d2cdd87037b9f0c387228d7d4743da4869929c93)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit 0f7c6c580ef0de60af68fd22bce36c0c0b2515b0)
|
| |
| |
| |
| | |
(This used to be ctdb commit 15d8308e5a0ce04351d70ac3dd25c7698931ebba)
|
| |
| |
| |
| |
| |
| | |
into ctdb bzr tree
(This used to be ctdb commit eaea8a9fa8d2f5e08f3af619fa1008a663f39053)
|
| |
| |
| |
| | |
(This used to be ctdb commit 46cd984500cd77d295f059132b4892dbfbc2bcd3)
|
| |
| |
| |
| | |
(This used to be ctdb commit 36d838801a2a2008c50322cdbfff65a308b1cd1a)
|
| |
| |
| |
| |
| |
| | |
cluster in turn
(This used to be ctdb commit 2fab9f96df2e5b5c51c860fd65caf0e926a63e34)
|
| |
| |
| |
| | |
(This used to be ctdb commit 172ee33306be2ef5ce17a5b9d7fbcc1f265a1b0b)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
attach to databases after the protocol has started. The daemon
broadcasts information on new databases to the other daemons.
This also eliminates the need for the client to know about the hash
between db name and db_id.
(This used to be ctdb commit 3bad91a9d987d4c09fe3322eac23c2733660ad08)
|
| |
| |
| |
| | |
(This used to be ctdb commit a2a3b254b22dbaafc8c4934d99cc67d6ae4adbd1)
|
| |
| |
| |
| |
| |
| | |
testing of ctdbd
(This used to be ctdb commit 05789da5818f8b20f04779b0df5125914d9047f6)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
for 2 days.
The main bug was in smbd, but there was a secondary (and more subtle)
bug in ctdb that the bug in smbd exposed. When we get send a dmaster
reply, we have to correctly update the dmaster in the recipient even
if the original requst has timed out, otherwise ctdbd can get into a
loop fighting over who will handle a key.
This patch also cleans up the packet allocation, and makes ctdbd
become a real daemon.
(This used to be ctdb commit 59405e59ef522b97d8e20e4b14310a217141ac7c)
|
| |
| |
| |
| |
| |
| | |
control
(This used to be ctdb commit c67f8a1783ce6f5af9940d2e22847ddcd939763d)
|
| |
| |
| |
| |
| |
| |
| | |
we should only write the pushed record if RSN of the new one if higher
than the rsn of the existing one not the other way around
(This used to be ctdb commit f535008c3755cf84acff7bc73ea05c0901e940ef)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
this is not optimized at all and copies/merges all records between
databases instead of only those records for which a certain node is
lmaster. (step 7 should later be enhanced to a, delete the database,
push only those records for which the node is lmaster)
(This used to be ctdb commit 509d2c71169e96a8610f9db91293dc7a73c2cc10)
|
| |
| |
| |
| |
| |
| | |
another node
(This used to be ctdb commit c313daff4c1362cd08a9f682ce04cab312678038)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit a84e9b47a87fc7d4756b4a179aa2ea0bc7c54c78)
|
| |
| |
| |
| | |
(This used to be ctdb commit ec342b667a085a5c740fbeec8882070571071862)
|
| |
| |
| |
| | |
(This used to be ctdb commit ef0027faa631b00c7fc1a7c4538fbf3080248f0b)
|
| |
| |
| |
| | |
(This used to be ctdb commit 95db9afa7dd039e1700e2f3078782f6ac66e9f51)
|
| |
| |
| |
| | |
(This used to be ctdb commit e5a98eee991a7926ddb6964ea3785b11303d175e)
|
| |
| |
| |
| | |
(This used to be ctdb commit b4efdd1944207e51dccd6cd5e50f451a7dddcd91)
|
| |
| |
| |
| | |
(This used to be ctdb commit 7f902f6c4270adc0543096c78415d335b88d6232)
|
| |
| |
| |
| | |
(This used to be ctdb commit d19be7ea56003faffcb3fb8a76fd804df0431242)
|
| |
| |
| |
| | |
(This used to be ctdb commit 9deaa1892faa8288cad9f6fde20d2aa8ba8af699)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 521484a462dcddeebe02bb9c725e18939919b6fe)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
while recovery is in progress the daemon will discard all CTDB_REQ_CALL
and rely on clients retransmitting them
add new controls to get/set the recovery mode
(This used to be ctdb commit 41458a61577885ac49150f830e92e93e634c5411)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
it does not yet work since ctdb_control can right now only be called
from client context and the pull is implemented as the target ctdb node
itself using a get_keys to pull the keys from the source node thus
ctdb daemon needs to ctdb_control to a remote node
(This used to be ctdb commit a55c7c64b4ff87f54b90649c9f469b1ff36dc9ea)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 6664e00fc02e1c60cc1a35ecd15f4893a34f23d1)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit fd0d2385206b0329b74d908f3bdf89d3f32095d1)
|
| | |
| | |
| | |
| | |
| | |
| | | |
key/lmaster/header and data
(This used to be ctdb commit ac00d6271ba6356c1edf804df44d0d2600791610)
|
| |/|
| |/
|/|
| |
| |
| |
| | |
fix the logic in ctdb_connected to print CONNECTED if the node is
connected and UNAVAILABLE when the node is dead instead of the opposite
(This used to be ctdb commit 0f431d2f3e0bd94d10fe77e56cf0ed6c48402400)
|
| |
| |
| |
| | |
(This used to be ctdb commit 2c37cc7bb97dee5bb2e929958e6c834b27c9ae6a)
|
| |
| |
| |
| | |
(This used to be ctdb commit b5434a40cf2db008eb1e681fcd2ceeff331324fa)
|
| |
| |
| |
| | |
(This used to be ctdb commit b69fb43643993ee5aaabf8711bb874f95d468f35)
|
| |
| |
| |
| | |
(This used to be ctdb commit 89512fd659c5b1dc450b7162ca985a7083fd40ac)
|
| |
| |
| |
| | |
(This used to be ctdb commit 751c1365ab55a217ff33d985d52bd26581578617)
|
| |
| |
| |
| | |
(This used to be ctdb commit d130e02936ea4bdcd3a6f02c53be4b7771993138)
|
| |
| |
| |
| |
| |
| | |
client
(This used to be ctdb commit cbd01fc8978f798a5eb5c8920a1acb68d43f7a80)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit 6ca7caa90f4aa7fa2753f6ee9090d629cdb63871)
|
| |
| |
| |
| | |
(This used to be ctdb commit 4cbaf22cc4bede8c95dd9b87e21bbe886307e23b)
|
|\|
| |
| |
| | |
(This used to be ctdb commit 9253714401de1d7fea6ad44c35f324004683abd7)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
(This used to be ctdb commit 4c197f1cbfdd5f65af9c059aae2b4508ebd0cd34)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the cluster is currently in.
remove all instances where the clients try to fill in the generation
field of the header
(This used to be ctdb commit fd75463f69f9f9100b2fe4cb710201a8262cdcec)
|
| |
| |
| |
| |
| |
| |
| | |
this will allow a node to verify that a received pdu is sent from a node
in the same generation instance of a cluster.
(This used to be ctdb commit e32d3ca9a622237c4e2622de98825c0962760d48)
|
| |
| |
| |
| | |
(This used to be ctdb commit f24f043a18082d21ba240a73de9daab50cd442a5)
|
| |
| |
| |
| | |
(This used to be ctdb commit 47b53d344941a3203c87788439e7df59477681be)
|
|\|
| |
| |
| | |
(This used to be ctdb commit d21de127cceea7174b2e05701c8846c0b0c881c0)
|