| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
such daemons in a 2 node cluster.
create a small test application that connects to the ctdb daemon at /tmp/ctdb.socket.127.0.0.1 and do some commands to the daemon.
currently this test tool only opens the socket and registers its pid with the daemon
(the daemon needs to know the pid so that it can forward messages to the correct client)
the test will be extended with additional ctdb commands
(This used to be ctdb commit 801f6127cdd50c5b2d0e64dd8db08500af9dadc9)
|
| |
| |
| |
| | |
(This used to be ctdb commit 2f4e7e34071c8950f6c4d64469c5eb15d0888113)
|
| |
| |
| |
| | |
(This used to be ctdb commit 36980878141c5e506dd7ee021fba6ca7d0ff5ad3)
|
| |
| |
| |
| | |
(This used to be ctdb commit 8d110df5939b3e6a6341909956453887f4eb6b0d)
|
| |
| |
| |
| | |
(This used to be ctdb commit 325afd2de2f5a96fb4f8ec624e04f253c712c97d)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit e605417436855d22343462acae4cbb79a374977e)
|
| |\ \
| |/ /
|/| |
| | |
| | |
| | | |
add code to actually pass the messages between clients and ctdb
(This used to be ctdb commit 6d5b55d7b9c611fb5e98765906757a7d82e4bf6b)
|
|/ /
| |
| |
| |
| |
| | |
both daemon and standalone mode. Does not compile\! committing so ronnie can continue while I'm out
(This used to be ctdb commit 1b5e65a700e2bd0a5c913d7866024b25600a14c9)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit a027d468f39fdd95a4bd03e26da90eb229b2a645)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 136f912562ef00ede5589a7aa080503538d14bc3)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- split client specific routines out of ctdb_daemon.c
- use ctdb_queue code in message send from client to daemon
- use clearer names in client/daemon functions
- use talloc autofree context to avoid global for unlink of socket on
exit
- start on API change for message handler, to allow ctdb messaging to
handle daemon mode with multiple clients
(This used to be ctdb commit 53555db45f3583ae4a32cc3aa9e07fb8ef2a77e3)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 55f1c2442a53a547302669a4fdd0f1c1deeed930)
|
| | |
| | |
| | |
| | |
| | |
| | | |
more obvious
(This used to be ctdb commit 350f14909d5dba6cd9d76d221e263933926cea6c)
|
|/ /
| |
| |
| |
| |
| | |
store this pid inside the client structure in the ctdb daemon
(This used to be ctdb commit d4499c5e0403b0348fa36b259164b1cbfcd671b8)
|
| |
| |
| |
| | |
(This used to be ctdb commit 8d09cac96b2c604a68e4903346cc9db3a66d80da)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 886a3e9122168ececc257aa1bef2f5de2f2d8d7e)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 050f302103b32ea3895fc97dae7726f11fbf01e3)
|
| | |
| | |
| | |
| | |
| | |
| | | |
abstract IO via ctdb_queue_*() functions
(This used to be ctdb commit 636ae76f4632b29231db87be32c9114f58b37840)
|
|\| |
| | |
| | |
| | | |
(This used to be ctdb commit 18d6e58b92f59f18cd7772cdbc1b8812a8609ab4)
|
| | |
| | |
| | |
| | |
| | |
| | | |
read thing explicitely
(This used to be ctdb commit 6156bec0187df27578afd5afa3fcaadb1a202030)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit b1e71018866752d32f59170fd5c8ba01b05694d9)
|
|\| |
| | |
| | |
| | | |
(This used to be ctdb commit fb06332c246e9f8b98a6391b4eda183e2f03333f)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 44f3e4456d931af642192e034f84c961ab1fdcf0)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 5e2e6a5ce439762876f2aa054fdd0d4bb54c403c)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
we can no longer use this function from the application if we are in daemon mode.
add a horrible "sleep()" to ctdb_test.c to prevent the daemon from dissapearing (parent process died) when the application exits which may happen before the other nodes in the test have finished talking to our daemon
(This used to be ctdb commit 74d35dafe06d71e755f3a58cc58d4b9b56fc821b)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 2f685c68e0b17ed8a290a265ebd64c1d089ceec5)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit d476aa8533b394af6aced9c80fffaf0eefae1dd0)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
the same in both modes to a client.
send the correct structure back to a client
assorted other cleanups
(tests/test1.sh now works in daemon mode)
(This used to be ctdb commit f4593754cab750dfdb9384884502e2e1b8fde1f0)
|
| | |
| | |
| | |
| | |
| | |
| | | |
does not yet work
(This used to be ctdb commit ff428808c6546d6f2804a1ac1cf414d1bb9cdcb4)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 55bc7ee10b9e9df32792b6b5779f094eb513069e)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit e516ea4714ae0b84ae6073201fbe297dd49b8c51)
|
| |
| |
| |
| | |
(This used to be ctdb commit 10466fe11da71c93fa764bea2b3e1e741c113f9c)
|
| |
| |
| |
| | |
(This used to be ctdb commit d883c1bbd4d3691a0787d37c226051f4fce4d45d)
|
| |
| |
| |
| | |
(This used to be ctdb commit 2ba2522f2def3032c89c7973915610a245842b07)
|
| |
| |
| |
| | |
(This used to be ctdb commit 6dbb36f27dd0f8ac00c7a010108d4fba15753479)
|
| |
| |
| |
| | |
(This used to be ctdb commit 8366c212bde710dd46c8c1d9d4301f6c3738e300)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 079b88102a4c9fc56d12a6c6f74366412731bced)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to set our source side to the same ip address as we use to listen to ctdb traffic.
We need this since there is no guarantee that INADDR_ANY (which would be defaulted to if we dont bind) would be routable from the remote host.
This is entirely possible to happen since CTDB traffic is likely to be isolated to a private non-routable network.
(This used to be ctdb commit e0743d2f84ca0088734c912e210deb93a6b78860)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit 83b794befd8d34b3da544a483f9d39a3fa140655)
|
| |
| |
| |
| | |
(This used to be ctdb commit ac6ac290e79446f52caf31f429b4c38668c27eda)
|
| |
| |
| |
| | |
(This used to be ctdb commit b946ff61c0e4b3269d3c7e01093d0a6d5215d6ee)
|
| |
| |
| |
| |
| |
| | |
the same context.
(This used to be ctdb commit d995103143f6f13f59118549d93ab4b29c27ec89)
|
|/
|
|
|
|
| |
it sent message in both (or all) direction at the same time. Now it measures normal pingpong.
(This used to be ctdb commit 26646aa91eb4e31efe6bacd92806ef7477b03bb7)
|
|
|
|
|
|
|
|
| |
Workaround is because I couldn't find a correct way in ib to reconnect cleanly (with queue kept) when destination is unreachable.
When connection is broken, all internal queue contents are being destroyed and reconnects automatically.
An "external" send queue is kept until the connection is up again for a dest node.
(This used to be ctdb commit 49cac6eafb9d9c80ef1c7f0388aa7786c8be6f24)
|
|\
| |
| |
| | |
(This used to be ctdb commit fcf2f4783842edb3e91a62941aee62e24c19024c)
|
| |
| |
| |
| |
| |
| | |
added TCP_NODELAY on tcp sockets
(This used to be ctdb commit fa76cff388237adea98c2be0827c54334080256a)
|
| |
| |
| |
| | |
(This used to be ctdb commit 4c1434cc4613fc94958de0aa882bf7ca41ec8458)
|
| |
| |
| |
| | |
(This used to be ctdb commit bb1a80492851c380fb239ce294fc1fae697006a0)
|
| |
| |
| |
| | |
(This used to be ctdb commit 7eeeb9c1d8f82739015ce78d8c90291baf3b1982)
|
| |
| |
| |
| | |
(This used to be ctdb commit 5c45b51ec42cdbadce7870b47b765a79d8d41b8b)
|