| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
change ctdb_client_fetch_lock to return a status code instead of a record handle and make it unconditionally fill in data.
change ctdb_client_store_unlock to take ctdb_db and key as arguments instead of a record handle
update the ctdb_fetch.c test to use the clientside helpers for fetching and storing data
(This used to be ctdb commit 22d5d40375e0135916c97945646f94119612615d)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit edf1e1fea8500461a08cd2795251a5cc0bd10229)
|
| |\ \
| | | |
| | | |
| | | | |
(This used to be ctdb commit fcf3669c27691ddb383d1c585234622efa498d90)
|
| | | |
| | | |
| | | |
| | | | |
(This used to be ctdb commit c4747460a8e0017acfd2a97a632ecd9395562d4f)
|
| | | |
| | | |
| | | |
| | | | |
(This used to be ctdb commit 1952be19f625dbe257050acebf468e7e6eb0da8c)
|
| |/ /
|/| |
| | |
| | | |
(This used to be ctdb commit 87dd265d2c61125ca2fa922cfcf9371a234fff0c)
|
|/ /
| |
| |
| |
| |
| | |
occured in the client or in the daemon
(This used to be ctdb commit a7e42c2c56e38b4b58ede0ad45767695d704dac4)
|
| |
| |
| |
| | |
(This used to be ctdb commit 7c749315130a2bc87dcc07460d10dcb089ae4202)
|
| |
| |
| |
| | |
(This used to be ctdb commit e0c9844ea6270ff506b0b5906aa6ccfcc3bcce7a)
|
| |
| |
| |
| | |
(This used to be ctdb commit e293f6fadf673d8bc7203198d709bcb28c26b482)
|
| |
| |
| |
| | |
(This used to be ctdb commit 0feb5da60c0331f6c391622910ca1f436263ce46)
|
| |
| |
| |
| | |
(This used to be ctdb commit 27b67ee6576b17f8b3aae024ae3bd0bb1c42f0f2)
|
| |
| |
| |
| |
| |
| |
| | |
this will be the core of the non-blocking lock idea for ctdb, it will be used
in place of ctdb_ltdb_fetch(), but will also get a lock. It re-starts a request
if it needs to block
(This used to be ctdb commit afa479026cf6293e6a878c8a329cdac035284672)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit 15e18293eaa5ddcd325395213014b5a4498ca309)
|
| |
| |
| |
| | |
(This used to be ctdb commit 6587bdca71d97709c9271a73aea0be5a2a35f399)
|
| |
| |
| |
| | |
(This used to be ctdb commit d4619ce98ce44acaebeb6ae9c516a7917bf4e27f)
|
| |
| |
| |
| | |
(This used to be ctdb commit 512a96de1b31e856785749ffc0bed60b1c589f9e)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The problem we have is this:
- we want the client smbd processes to be able to 'shortcut' access
to the ltdb, by directly accessing the ltdb, and if the header of
the record shows we are the dmaster then process immediately, with
no overhead of talking across the unix domain socket
- a client doing a shortcut will use tdb_chainlock() to lock the
record while processing
- we want the main ctdb daemon to be able to set locks on the
record, and when those locks collide with a 'shortcut' fcntl lock,
we want the ctdb daemon to keep processing other operations
- we don't want to have to send a message from a smbd client to the
ctdbd each time it releases a lock
The solution is shown in this example. Note that the expensive fork()
and blocking lock is only paid in case of contention, so in the median
case I think this is zero cost.
(This used to be ctdb commit a3248c3e2b740cd2403acffd3c1f6a33dca0ea03)
|
| |
| |
| |
| | |
(This used to be ctdb commit 541814e6ee3dd7f8f1b3fb615213ff5979b6e22f)
|
| |
| |
| |
| | |
(This used to be ctdb commit de3db72c1fd0e56ac2b8d8fe962c725dc64f2051)
|
| |
| |
| |
| | |
(This used to be ctdb commit 43cd05ab58e940a1ef0352aabe0b63075264a7a0)
|
| |
| |
| |
| |
| |
| |
| | |
- when we do a store_unlock the lock record becomes unlocked, so we
must destroy it (or we leak memory)
(This used to be ctdb commit d85955640e670dd580073da96b25fb8a10c08d18)
|
| |
| |
| |
| |
| |
| | |
on the command line
(This used to be ctdb commit a19df59e9c2ea24d92a483f8a44514f492d49601)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
fetch_lock the same record
they both successfully fetch and lock the same record at this stage but when the actual locking works properly the second child will block.
this test allows us to verify the blocking once we have implemented it
(This used to be ctdb commit b1c0baa03a669757aaacb6e1a2794224f5ba2cd7)
|
| |
| |
| |
| |
| |
| | |
note that the actual locking/unl;ocking does not still work
(This used to be ctdb commit 45505520a69a2fbbb1e3a015b54d2133924f46a4)
|
| |
| |
| |
| |
| |
| | |
there is still a bug in the ctdb code in that the children no longer receive messages from the parent for unknown reasons
(This used to be ctdb commit 468f68e4607900c5c38aea428a48dd6ea1647411)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 9c4e5569b82d9c7894e3ac1d5f0783c4d770daf4)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 080b6901173afb2ad618dd0621876ff478c7d6e5)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
stored in ltdb
this makes it possible to do fetch_lock and store_unlock across a domain socket to read/write data.
note that the actual locking is NOT implemented yet
(This used to be ctdb commit c7a397c56caf71283c081e5b97620085ed5108c6)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
for now:
fetch a record
store a known entry for this record
fetch the record again (and later verify we got the same record)
store it back again
this will not work right now since we dont yet store the record inside the daemon
(This used to be ctdb commit f502094499a3c25ab58aa3d192588b5e6dd2b8e4)
|
| |
| |
| |
| |
| |
| |
| |
| | |
note that the store_unlock does not actually do anything yet apart from passing the pdu from client to daemon and daemon responds.
next is to make sure the daemon actually stores the data in a database
(This used to be ctdb commit 167d6993e78f6a1d0f6607ef66925a14993ae6a1)
|
| |
| |
| |
| | |
(This used to be ctdb commit 3753b64e4e64446dc1f20ec92b45ba11bc0e0be5)
|
| |
| |
| |
| |
| |
| | |
right now this test only does one fetch lock but this will be enhanced as more code is added to ctdb to handle fetch_lock and store_unlock
(This used to be ctdb commit 996f117d9181dee22aea979ce04333035f5522c7)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
we cant peek in state->c since this is uninitialized
and even if it were not it would be wrong
create a new structure to pass BOTH client and also the reqid to respond back to
the client with
(This used to be ctdb commit e1a0da3dfbb4a927e8d98723b5e51a201c2a3428)
|
| |
| |
| |
| | |
(This used to be ctdb commit e193d69cd8cdd293379ab88d25e6984b584afa22)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
no locking is yet done and the store_unlock call is still missing
the ./tests/fetch.sh --daemon test fails with parent process dying which needs to be investigated.
(This used to be ctdb commit 7d7141c968950a8856f1be79871932b688bfb07f)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 8b5233fbe773893d1bc6b377f8956fe0b3e503ab)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 78cf4443ac0c66fb750ef6919bcdec189ac219c9)
|
| |\ \
| | | |
| | | |
| | | | |
(This used to be ctdb commit 63a59a700a1fb4c23cd76d99c5b4c9660c7ca475)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Volker
(This used to be ctdb commit b7f134fe6e160d7ec70c466f8f3e7fb3dabd0774)
|
| | | |
| | | |
| | | |
| | | | |
(This used to be ctdb commit 9723828b1562eb6a386eb26e63db3b6617ebb454)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
instead of event_loop_wait() since the latter will return and thus take down the daemon
(This used to be ctdb commit 26ffd166c176deb7e2437f3ee87887f8b57435e7)
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
is also passed from originator to receiver
(This used to be ctdb commit f9c2ed3cff8eb481bfa80d944d86233e2a7d5d00)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit e49a6436483bffcf867fbb746ef43a5356055857)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit 4c660b9706ef09527b8e1a2837d844d30672c541)
|
| |
| |
| |
| |
| |
| |
| | |
read returns 0 bytes this means the client has exited. Close the connection
then.
(This used to be ctdb commit bd10f4e62146493848258df8a3dc3b9222337a12)
|
| |
| |
| |
| | |
(This used to be ctdb commit b84f97adfd25b2fbfab1c7964b68931643e8029c)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(send a message to ourself)
this unfortunately terminates the ctdb daemon when running but im too tired right now to debug it.
checkin so that nothing gets lost overnight.
(This used to be ctdb commit 9d8821bfd1456591fb5c31f0c6c3fd63e99dc4fb)
|
| |
| |
| |
| | |
(This used to be ctdb commit c54c87feb89b8d97655c1fcd748a295119a1171f)
|
| |
| |
| |
| |
| |
| | |
non-ctdb-linked clients what the vnn of the local cluster daemon is
(This used to be ctdb commit 57fd1aa54b234545e1e465b5ace2ce93fcfbc22a)
|