| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
defer it for one second and try again
(This used to be ctdb commit 606fb6414b97d1813056982cda7c0fe84d746e67)
|
|\|
| |
| |
| | |
(This used to be ctdb commit f67a4842e7b1efb2ad61c41e4895c7698e564bf3)
|
| |
| |
| |
| |
| |
| |
| | |
update the recovery test script to start all ctdb daemons with a
recovery daemon
(This used to be ctdb commit 47794e16df285cacefc30208d892d931a6e46b96)
|
| |
| |
| |
| | |
(This used to be ctdb commit b0cf919e4f38961e5cf4e1e79a0cfe4bb4a96d76)
|
| |
| |
| |
| | |
(This used to be ctdb commit b45936828713c31ee670e2106b49c2351234f310)
|
| |
| |
| |
| |
| |
| | |
shortcut from working
(This used to be ctdb commit 5e18930be8c0efb87aa9e2780d9457634b24e156)
|
| |
| |
| |
| | |
(This used to be ctdb commit f1188289c18805c2c5f8bae61d73df3fc762faee)
|
|/
|
|
|
|
| |
the new seqnum code
(This used to be ctdb commit 6109ae3dae8d93c93a2dc76cc561ea6e21458aa6)
|
|
|
|
|
|
|
| |
free it and also we wont accidentally return from the function without
killing the event first
(This used to be ctdb commit e3d72d024ef7342a808e5c488fd646a39e5fac78)
|
|
|
|
|
|
|
|
|
| |
trigger
this must have been a sideeffect of a different bug in the recoverd.c
code that has now been fixed
(This used to be ctdb commit 676446fd1083c371ad0ff72dd8c636ec8e6d1423)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
election is primitive, it elects the lowest vnn as the recovery master
two new controls, to get/set recovery master for a node
to use recovery daemon, start one
./bin/recoverd --socket=ctdb.socket*
for each ctdb daemon
it has been briefly tested by deleting and adding nodes to a 4 node
cluster but needs more testing
(This used to be ctdb commit 541d1cc49d46d44042a31a8404d521412ef2fdb3)
|
|
|
|
|
|
| |
i.e. which node is "elected" to check for and drive recovery
(This used to be ctdb commit d577093eb4b619392c71ab5ce81e8c02565d93f0)
|
|
|
|
|
|
|
|
|
| |
recovery or not that all active nodes are in normal mode.
If we discover that some node is still in recoverymode it may indicate
that a previous recovery ended prematurely and thus we should start a
new recovery
(This used to be ctdb commit c15517872e6c98c8c425a8d47d2b348ecb0620b0)
|
|
|
|
| |
(This used to be ctdb commit 96082c54d830974bf9a4d5bad33ad60379a85798)
|
|
|
|
| |
(This used to be ctdb commit 6edb9149c7eb36da47e4e6a9dd3ede22263ce3f9)
|
|
|
|
|
|
| |
function
(This used to be ctdb commit 81d39177949b54715710907d14ddc888dc09b064)
|
|
|
|
|
|
| |
onto the remote nodes
(This used to be ctdb commit 1ba76d374652cfa29e56fb77c7190349e42d3bcc)
|
|
|
|
| |
(This used to be ctdb commit 75096dde58df6532abbf5b9ebd771e8810156483)
|
|
|
|
|
|
| |
into a separate helper function
(This used to be ctdb commit d5ab30d0ac21e736eb34eaa19bccfee5f0ce7cfb)
|
|
|
|
|
|
| |
databases onto the local node
(This used to be ctdb commit 5cecc47449c369f91e83389a94b987ac32b1e3f4)
|
|
|
|
|
|
| |
has all the databases that exist on any other remote node
(This used to be ctdb commit 0f436e3d40fea6e6a146019b0c664e80e81e88b4)
|
|
|
|
|
|
| |
during recovery
(This used to be ctdb commit 04758c6f7d8f61260be6d2472380cb7904984427)
|
|
|
|
|
|
| |
function
(This used to be ctdb commit dba4e4f8aa4f2fde1e9f8d93bdf3a33f7de8ce18)
|
|
|
|
| |
(This used to be ctdb commit 07bc338e490e0f7018808a2450bc54863eb88c94)
|
|
|
|
| |
(This used to be ctdb commit 843e974b29c93df891ae7cf13323ee960a334f60)
|
|
|
|
|
|
|
| |
we really should kill the event in case the call completed before the
timeout so that we can also make timed_out non-static
(This used to be ctdb commit f297eed589b1d4e188f77f195683365cf91d0e62)
|
|
|
|
|
|
|
|
| |
since if the command times out and we return from ctdb_control we may
have events that can trigger later which will overwrite data that is no
longer in our stackframe
(This used to be ctdb commit 93942543092be618c0bd8ef68b470b0789bad7ad)
|
|
|
|
|
|
|
|
| |
ctdb_ctrl_ calls are timedout due to nodes arriving or leaving the
cluster it crashes the recovery daemon afterwards with a SEGV but no
useful stack backtrace
(This used to be ctdb commit cd3abc7349e86555ccd87cd47a1dcc2adad2f46c)
|
|
|
|
|
|
|
|
|
| |
start the daemons with explicit socketnames and explicit ip address/port
remove all --socket= from all ctdb_control calls since they are not
needed anymore
(This used to be ctdb commit 593a959d428f5b4a913117a9b5c8fe65a3eb950e)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of traversing the full cluster.
this makes it easier to debug recovery
update the test script for recovery to reflect the newish signatures to
ctdb_control
the catdb control does still segfault however when there are missing
nodes in the cluster as there are toward the end of the recovery test
(This used to be ctdb commit 8de2a97c14a444f817ceb36461314f10c9601ecc)
|
|\
| |
| |
| | |
(This used to be ctdb commit 08173e3ab77178b9841db0081a51b93291d9e8dc)
|
| |
| |
| |
| | |
(This used to be ctdb commit 8076a7c7e12da6d59bae31a2e4a0267d87c7b1b3)
|
| |\
| | |
| | |
| | | |
(This used to be ctdb commit c0fa029435fdaa0be006b28eddb6b31beb2ee605)
|
| | |
| | |
| | |
| | |
| | |
| | | |
- use the tdb_chainlock_mark() call to allow us to guarantee forward progress in the ctdb_lockwait code
(This used to be ctdb commit e201e98aad0fef6a779a80f3b1ae7792953e2d6b)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 2fe976d7a376a763472cc7952a78b6249ce416c8)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit fec779711e8c4d6e047d792aee744e60e5a9f67c)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to close the fd automatically when a fd_event is freed. This prevents races which can lead to epoll missing events
- added autoconf rules for automatically building with epoll support
(This used to be ctdb commit 4d113298b26f7163992f2e47429c953bd4f957c9)
|
| | |
| | |
| | |
| | |
| | |
| | | |
without actually locking it. This will be used to guarantee forward progress in the ctdb non-blocking lockwait code
(This used to be ctdb commit 2af98c3418496b39106c7282f550049ec8239657)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
this makes it possible to kill a specific daemon in the recover test
script
(This used to be ctdb commit 2fa394b4c80988cb1a6d04b236ec64cc9d9e8a40)
|
|\| |
| |/
|/|
| | |
(This used to be ctdb commit 8648104f8d76d22427c14422b126f7e979cc2d95)
|
| |
| |
| |
| | |
(This used to be ctdb commit 99765bbe327bfe9c43415f4943281458f25be51b)
|
|/
|
|
|
|
|
|
|
|
|
| |
one broadcast address for all nodes
and one broadcast address for all nodes in the current vnnmap
update all useage of the old flag to now only broadcast to the vnnmap
except for tools/ctdb_control where it makes more sense to broadcast to
all nodes
(This used to be ctdb commit dfb65b88cf67ad9d61268c4b47a6d8ae346f47df)
|
|
|
|
| |
(This used to be ctdb commit 44fdafaf421e3e906796d529aed2f7c5df201b94)
|
|
|
|
|
|
| |
- added total memory used to ctdb_control status output
(This used to be ctdb commit a99ffe4372edc63d83d8c8ebf9a60b3413301f5a)
|
|
|
|
| |
(This used to be ctdb commit 858061372fc9902837a1a5b8bcfc0ada58eec193)
|
|\
| |
| |
| | |
(This used to be ctdb commit 62574808ef4dcb76760f1dd2496fbe8e34197c23)
|
| |
| |
| |
| | |
(This used to be ctdb commit be2572b1b09eaaa1ea6a726d60f16996f9407d13)
|
| |
| |
| |
| | |
(This used to be ctdb commit c66920d9fb08a4a33418e2c1dcf1fc320fba3761)
|
| |
| |
| |
| | |
(This used to be ctdb commit 1f89da231c6637e339d5da156d6a48340706fe61)
|
|\|
| |
| |
| | |
(This used to be ctdb commit 6c8b90cedc67daa89d54db5268fde18bfc20abaf)
|