| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This patch changes the callback signature for traversal
functions to allow a client to abort a traverse before it finishes.
Updates to all callers and examples as well as rb-test tool.
(This used to be ctdb commit 8ab0c63ad36cfbbb1e5fed46a1f4c47b1fdb581f)
|
|
|
|
| |
(This used to be ctdb commit e7b57d38cf7255be823a223cf15b7526285b4f1c)
|
|
|
|
| |
(This used to be ctdb commit df0e7a4aa13112d613702d8ea0fb0e18510d293c)
|
|
|
|
| |
(This used to be ctdb commit 26f2ee2b754a9271454412f05111a19b3013c6eb)
|
|
|
|
| |
(This used to be ctdb commit 38aa759aa88a042c31b401551f6a713fb7bbe84e)
|
|
controls to register/unregister/check a server id.
a server id consists of TYPE:VNN:ID where type is specific to the
application. VNN is the node where the serverid was registered and ID
might be a node unique identifier such as a pid or similar.
Clients can register a server id for themself at the local ctdb daemon.
When a client dissappears or when the domain socket connection for the
client drops then any and all server ids registered across that domain
socket will also be automatically removed from the store.
clients can register as many server_ids as they want at the same time
but each TYPE:VNN:ID must be globally unique.
Clients have the option of explicitely unregister a server id by using
the UNREGISTER control.
Registration and unregistration can only be done by clients to the local
daemon. clients can not register their server id to a remote node.
clients can check if a server id does exist on any ctdb node in the
network by using the check control
(This used to be ctdb commit d44798feec26147c5cc05922cb2186f0ef0307be)
|