| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
ctdb_cmdline_client() and ctdb_attach()
(This used to be ctdb commit 14656eaa01a8951693fa146b3d35258f7daaafd5)
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
Makefile.in
tools/ctdb.c
(This used to be ctdb commit 0fedef0ffba4178126eee9544c5e2db52f5db893)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 1a766382d7d774aa3444e07401575e51d3704dba)
|
| | |
| | |
| | |
| | |
| | |
| | | |
let all databases default to not support this until enabled through this control
(This used to be ctdb commit 908a07c42e5135a3ba30a625fc4f4e4916de197a)
|
| | |
| | |
| | |
| | |
| | |
| | | |
setting in ctdb getdbmap output
(This used to be ctdb commit 4cac9ad7d9c9ca657a247a6c215476399c7d2210)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
of a boolean for
the persistent flag.
This is the same size as the original boolean but allows ut to add additional flags for the database
(This used to be ctdb commit 7462761638d25880ad46024ad4ef21667eb99a98)
|
| | |
| | |
| | |
| | |
| | |
| | | |
but before we learn the pnn of the local node
(This used to be ctdb commit 8d363d3ce105b78c94f8e50184b6579b25b237f6)
|
| | |
| | |
| | |
| | |
| | |
| | | |
of the old client
(This used to be ctdb commit 231f16b3e0c9c44fc85c95bde7951ccfab50af91)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 0893fa0f3257f50d54896ffa78ec12ee11e8c6d2)
|
| | |
| | |
| | |
| | |
| | |
| | | |
or not
(This used to be ctdb commit 01314c2cb3a480917d6a632b83c39f0a48bba0e7)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit a47ae3c2c81c62989bc99455459069149c853bbd)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 7af255551f058d1f6bfdd38ca603e7a19d1bb7ba)
|
| | |
| | |
| | |
| | |
| | |
| | | |
dmaster and also have delegations active we must send a CALL to the local daemon to trigger it to revoke the delegations
(This used to be ctdb commit 1b7d42c3425e39dd2a1c4460e8a01fb1ea4a513c)
|
| | |
| | |
| | |
| | |
| | |
| | | |
routine that can do either normal or readonly fetchlock
(This used to be ctdb commit 6d5d79367f7d04e2a9a6ad5d8be70d609b764629)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 72a6e77fe56a4a6d11b1d02fa049b6dd347ac0f1)
|
| | |
| | |
| | |
| | |
| | |
| | | |
delegation and lock the record once
(This used to be ctdb commit 29c77c249d0454057ce28003e018e126c7c01513)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 6fccc902bce21fa6ff13ed08ee3341bbf8be39f2)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 8551420fb331dd2a897f4619278a981fcefb96e8)
|
| | |
| | |
| | |
| | |
| | |
| | | |
and revoking of delegation to the processing loop for CALL requests coming in from a local client via domain socket
(This used to be ctdb commit e7cbf5b5d03cc26a73a92066a651f8eab73624b8)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
requests to the processing loop for CALL packets we receive from different nodes.
This implements the ReadOnly and ReadWrite request processing, delegation and revoking of delegations for all requests coming in across the network from a remote node.
(This used to be ctdb commit 78f2c2ea70e6270cec59db7c3f174a511bf608a9)
|
| | |
| | |
| | |
| | |
| | |
| | | |
processes and trigger the destructors for all deferred calls to re-queue the original packets to the input packet processing function
(This used to be ctdb commit 530a78aa05910beeca0867c4dbe226d4ce73f946)
|
| | |
| | |
| | |
| | |
| | |
| | | |
all previous delegations, add a 1 second grace/delay for any new readonly delegation requests so that the read-write fetch-lock porcess has a chance to make progress
(This used to be ctdb commit 2a4e9e69850d64dd8aef695f587ebe04393a688f)
|
| | |
| | |
| | |
| | |
| | |
| | | |
wants a readonly delegation
(This used to be ctdb commit a3f54a556e97170eedf43708d58dd32446ca5840)
|
| | |
| | |
| | |
| | |
| | |
| | | |
This triggers a child process to be created to perform the actual potentially blocking calls that are required.
(This used to be ctdb commit 7d575ee92c95bc4aab78a33bc1aac7ff0811ab3a)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
deferal of processing of CALL commands.
Once the contexts are freed, the deferred calls are re-issued to the input packet processing functions again.
This is needed when/if a CALL can not currently be processed by the main engine due to the record being locked down for revoking of all delegations.
The data is passed through several layers of callbacks, and finally a timed event callback to ensure that the processing of the packet will be restarted again at the topmost eventloop, avoinding event loop nesting.
(This used to be ctdb commit cc6f78efcfa3b8caeffbd68018e6dfbf81488dce)
|
| | |
| | |
| | |
| | |
| | |
| | | |
write the record and header back to the tdb (for example we do when performing dmaster migrations)
(This used to be ctdb commit b935e83255aeb3754b2fd37cf5611e02f7283514)
|
| | |
| | |
| | |
| | |
| | |
| | | |
tracking database used to track delegations and revoke. This is because the recovery will implicitely result in a revoke of all delegations.
(This used to be ctdb commit b5520933b9922d6af6f59f535824e1cdacb9f774)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
database supports readonly operations or not. Add a private lock-less tdb file to the ctdb_db_context to use for tracking delegarions for records
Assume all databases will support readonly mode for now and se thte flag for all databases. At later stage we will add support to control on a per database level whether delegations will be supported or not.
(This used to be ctdb commit 502f86f79944df4bac9094f716e54110c511dc24)
|
| | |
| | |
| | |
| | |
| | |
| | | |
readonly delegations and revoke
(This used to be ctdb commit 9985a97e11688f3f688bb84e1180fd57c42077f4)
|
| | |
| | |
| | |
| | |
| | |
| | | |
The API for this function has changed since the 1.2 branch where readonly locks are being merged from
(This used to be ctdb commit d01b9716d3e50f4c6d102e8411f0401b0f499699)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
catdb' in that 'cattdb' will always traverse the local tdb file only, while 'catdb' does a cluster traverse.
Since some record flags may differ between nodes in the cluster when read only delegations are in use, cattdb is needed when you need to know the exact flag settings on the current node itself.
(This used to be ctdb commit d2342b680a3a8160d903d12550b86ee21c8b277d)
|
| | |
| | |
| | |
| | |
| | |
| | | |
to print its content.
(This used to be ctdb commit 5eaa9a8683babac27f9f0144ff4cb5364fcd54f6)
|
| | |
| | |
| | |
| | |
| | |
| | | |
of delegations
(This used to be ctdb commit 875b0bede217547b51f02648b6a28a3c98b6b949)
|
| | |
| | |
| | |
| | |
| | |
| | | |
the RSN by 10 and writes the new content to the record as sprintf("%d", rsn)
(This used to be ctdb commit 151b25798f2a2c182fc9557c1c1ea0f3ef0ad3fe)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 74a5b3d7bafd8827a4ee80095fde5798263821e4)
|
| | |
| | |
| | |
| | |
| | |
| | | |
enumerate the bitmap of nodes to where we have readonly delegations
(This used to be ctdb commit bfdeda30ee0e359f06dd5714864f8beae22b0736)
|
| | |
| | |
| | |
| | |
| | |
| | | |
nodes that we are tracking as having a readonly delegation
(This used to be ctdb commit d10084e62d37674bb8d9e31d457fd23e050545be)
|
| | |
| | |
| | |
| | |
| | |
| | | |
This function differs from the old FETCH in that this function will also fetch the record header and not just the record data
(This used to be ctdb commit c7196d16e8e03bb2a64be164d15a7502300eae0e)
|
| | |
| | |
| | |
| | |
| | |
| | | |
CQ S1028400
(This used to be ctdb commit 3ce1d3d6c8b8fd3097b8efd2c75797ed7682a562)
|
| |\ \
| | | |
| | | |
| | | | |
(This used to be ctdb commit 7bebfc7bad8f36e54003b8e25372fdaf54836e21)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rebase the CTDB PMDA from 1.0.114 to master:
- Add tevent and ctdb_protocol includes
- Handle latency metrics now stored under struct latency_counter
- Add new metric for the num_recoveries counter
(This used to be ctdb commit 2165a6f5117a71f9f97f46be9708fa34c037e17c)
|
| | | |
| | | |
| | | |
| | | | |
(This used to be ctdb commit b63333fb81aadc451df47c0c3c038e6165f0eac2)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also includes some code cleanup changes.
(This used to be ctdb commit 80ad2979804f5bba29020ace46e114a45fa6cb66)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently ctdb statistics are pulled in the PMDA fetch callback, which
results in a CTDB_CONTROL_STATISTICS call for each metric.
Do this once per fetch instead, and have the per-metric callbacks pull
data from the last counter cache.
(This used to be ctdb commit 137b498c75c55c966999cd788f12ed9010cfed3a)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Attempt to reconnect to ctdbd on fetch while it is unreachable.
We must provide our own queue callback wrapper, as ctdb_client_read_cb()
exits on transport failure.
(This used to be ctdb commit 28df6fbf1273b8d095a2bc38dca6a6c35c5c31bd)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The CTDB Performance Metrics Domain Agent (PMDA) is compiled when
Performance Co-Pilot (PCP) header files are present.
The CTDB PMDA periodically requests runtime counters from ctdbd (similar
to ctdb statistics) and exports these values via PCP for capture and
charting etc.
(This used to be ctdb commit fe7f69d6fc37661c2f1caa11de4ed3a7940d0a2f)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Regular "ctdb status" output flags which node is the local node, do the
same for machine readable output.
(This used to be ctdb commit 3885141f37724b3dea61b45fbac38489ec356588)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rather than using a fixed 2 second CTDB_CONTROL_GETDBPATH timeout.
(This used to be ctdb commit 9e178671560cb95121e11d718a76b05380ecd6c5)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Following connection to the local ctdbd, ctdb_cmdline_client() currently
issues a CTDB_CONTROL_GET_PNN request with a fixed 3 second timeout.
The ctdb cmd line client accepts a --timelimit argument for specifying
a per request timeout, pass this value through to ctdb_cmdline_client()
for use as a CTDB_CONTROL_GET_PNN request timeout.
(This used to be ctdb commit 0634d0305f42f17048b6830733767e8dc300e11c)
|
| |\ \ \
| | |/ /
| |/| |
| | | | |
(This used to be ctdb commit a3e8784bb107f7acd2a95913c1e6def52ce96105)
|