| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
non-daemon mode
remove the parameter from the ctdbd script
remove the store_unlock from ctdbd_test since there is no and will be no pdu for this
CTDB_REPLY_FETCH_LOCK no longer return the data for the record since the client is assumed to read this itself from the local tdb. remove some variables that no longer exists.
(This used to be ctdb commit 77c43479e1932b27387fc2f85a3cb6538633b481)
|
| |_|/ /
|/| | |
| | | |
| | | | |
(This used to be ctdb commit 506117dc24ec647c629c92a3996455cd8d9c8ec6)
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
fetch is now confined to the client code, no spcial code at
all in the daemon.
(This used to be ctdb commit 3ec801c9717e250b902760862df188e03c9bdbf4)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
version. The client version is different enough that this is
worthwhile
- enable local shortcut for client version of ctdb_call
- add idr_find_type(), with better error reporting in case of type
mismatch
(This used to be ctdb commit 2388094c5f7b6ce003e86b05620c06217d63b49c)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
us to put memory directly in the right context, avoiding quite a few
talloc_steal calls, and simplifying the code
- make the fetch lock code in the daemon fully async
(This used to be ctdb commit d98b4b4fcadad614861c0d44a3854d97b01d0f74)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a client held the chainlock, and the daemon received a dmaster reply
at the same time. The daemon would not be able to process the dmaster
reply, due to the lock, but the fetch lock cannot make progres until
the dmaster reply is processed.
The solution is to not hold the lock in the client while talking to
the daemon. The client has to retry the lock after the record has
migrated. This means that forward progress is not guaranteed. We'll
have to see if that matters in practice.
(This used to be ctdb commit 737e5a1253cb048222c595a474aff71c99fc554f)
|
| |
| |
| |
| |
| | |
- use TDB_CLEAR_IF_FIRST to ensure we don't use an old tdb
(This used to be ctdb commit ac47d7b4eb79597da1358da21f10e634cdc9dd2e)
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
to make the --dbdir option available to all ctdb tools, not just
the daemon
(This used to be ctdb commit add63b0ae11d8727163bb6f0c94a617d9b88ef28)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit bce40105e2ccbca5e364793bbf1a6357e6dd69b2)
|
| |
| |
| |
| |
| |
| | |
It ensures that when the client context goes away (such as when the client exits)
that any timed events and partially completed requests from that client also go away
(This used to be ctdb commit 45a45a0a44d4da9b45719aac72b0ae4bd4c74462)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 26037a7b3557faa1c10944f654b1465877c6b840)
|
| | |
| | |
| | |
| | |
| | |
| | | |
pdu any more
(This used to be ctdb commit 5bac32b3daf3c61214269cd09cfc1b6c3f8c3d6e)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit b49069aac0c14e5a02be843247930c197d620a81)
|
| |
| |
| |
| |
| |
| |
| |
| | |
occasionally leads to problems if an immediate send on the socket
causes a context switch and the client exiting before the daemon. We
now exit the client when the daemon goes away.
(This used to be ctdb commit b7bed0088e700f25105ceea63640b38804f51e4d)
|
| |
| |
| |
| | |
(This used to be ctdb commit 150153947b959f90991fdae8d7c85ef8d551dff5)
|
| |
| |
| |
| | |
(This used to be ctdb commit 67d3e64f82fd71ff1e32bf377d0cf1f636b9602f)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 6e6812641e3ce7afae7bd46ed317a885839fdd4f)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
this function can be used in test applications to perform an orderly shutdown of the ctdb cluster once the test has completed.
the ctdb nodes will remain operational until all of them have received a shutdown from their client(s) after which the ctdb daemons will all terminate.
this eliminates the need to using sleep() in some of the test applications
(This used to be ctdb commit f35db69dc190b11659aad85495bb66308fdb5599)
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
a ctdb cluster
(This used to be ctdb commit 00d2748bd4e7209ff7e253f6652fdd9bf16cf147)
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
(This used to be ctdb commit e83db4d76ea498413ba4314e937d0ff298bd4cb6)
|
|\| | | |
| |_|/ /
|/| | |
| | | | |
(This used to be ctdb commit 906419acf121ea93661f91bde65cdcd890f70e63)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
terminates while holding the lock and the next blocked waiting client is assigned the lock
(This used to be ctdb commit 927228299280779664683fca04a7f76b55bef813)
|
| | | |
| | | |
| | | |
| | | | |
(This used to be ctdb commit 5ef0cd83d7f24616dad85cece485b770376ecd45)
|
| |/ /
|/| |
| | |
| | | |
(This used to be ctdb commit a6477577beba71bd9185b968de43b763378f234b)
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- fixed memory leaks in the 3 packet receive routines. The problem was
that the ctdb_call logic would occasionally complete and free a
incoming packet, which would then be freed again in the packet
receive routine. The solution is to make the packet a child of a
temporary context in the receive routine then free that temporary
context. That allows other routines to keep or free the packet if
they want to, while allowing us to safely free it (via a free of the
temporary context) in the receive function
(This used to be ctdb commit 304aaaa7235febbe97ff9ecb43875b7265ac48cd)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 9fcc40a2ddd8f7f62bdd8b5ab71d182220e23af0)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 7497b5a9031c471c25bf6029c436fd82788b415c)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 1e2802422794956827263265306952df5e69b377)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit bf2799504498ae452bb7244ae3eb6a51797afe9b)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit 197a02384bd2ca42dfff4c0357175424d2321e9c)
|
| |
| |
| |
| | |
(This used to be ctdb commit b58d2ae0e4ef3393a93724526f2aebc7529de14f)
|
| |
| |
| |
| | |
(This used to be ctdb commit 79f3d63eec5652d87f13875c76e90ead81a26ad9)
|
| |
| |
| |
| | |
(This used to be ctdb commit 32b31a6b91a19fc0c5225cb88c35cc1d14b4a6df)
|
| |
| |
| |
| |
| |
| | |
add a basic debug system with -dXX
(This used to be ctdb commit af9f21cef79f888c57d3b50a23ca787c9567ce60)
|
| |
| |
| |
| | |
(This used to be ctdb commit 74028de89d18bfedcea17415d6d6dc2f7c69b076)
|
| |
| |
| |
| | |
(This used to be ctdb commit 598feb4fb9badcf329837965ad39e0f0dfe28498)
|
| |
| |
| |
| | |
(This used to be ctdb commit 3c5c433e5b92f8fe2193a6e5720e31e3eb6bc76b)
|
| |
| |
| |
| | |
(This used to be ctdb commit b2836974ad270e823c630e3acf12327b53c37d88)
|
| |
| |
| |
| | |
(This used to be ctdb commit 8e6a25f4c4a63145c0dee33453a0693dd395ee68)
|
| |
| |
| |
| | |
(This used to be ctdb commit f89ab3a06b4677f56c92768c3a8ae5ec9f5abbc2)
|
| |
| |
| |
| |
| |
| | |
new dmaster
(This used to be ctdb commit 6c48dcc5df7b855fc8e0774c9572c7b2af618348)
|
| |
| |
| |
| | |
(This used to be ctdb commit f4c8c4b3d4c6fb8f1b8e770d1788816af74a7e1f)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
fetch, to avoid the daemon re-reading it
- suffix the database name with the node name so that testing on
loopback doesn't result in a name collision in the database open
(This used to be ctdb commit ad30a4db75450643ff146c40faa306a021de3dd2)
|
| |
| |
| |
| | |
(This used to be ctdb commit c09054f878a88129abb6cce24c7bbf53f61a2648)
|
| |
| |
| |
| | |
(This used to be ctdb commit 02c09dc07c9bed57ca3692b14e41ac8cca0a29f4)
|
| |
| |
| |
| |
| |
| | |
disk file
(This used to be ctdb commit 5159f3a61f41bbaf563edd8d901a6bf5bfee4e4e)
|
| |
| |
| |
| | |
(This used to be ctdb commit 43061a4cf9b0995ebe6c86e27f7fc3aacb7bb23e)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
code. It may be added back later once everything is working nicely,
or simulated using a in-process pipe instead of a unix domain socket
- rewrote the ctdb_fetch_lock() code to follow the new design
(This used to be ctdb commit 5024dd1f305fe1ecc262db2240c56f773b4f28f0)
|
| |
| |
| |
| | |
(This used to be ctdb commit d8243f474897dc65fb7286225b07bdf48b6faed0)
|
| |
| |
| |
| | |
(This used to be ctdb commit 36c1e98a5533214d5507699dc5d8bdec35cb28c2)
|