| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
(This used to be commit 43ee3f8724164afc90a170c6da713b38d3995191)
|
|
(This used to be commit e2fe45cf4073b68e2a1c6577928d0765e26f3267)
|
|
(This used to be commit 141bd7ac39b66132f989d44d731512f939973f9e)
|
|
added opendb ctdb backend from ronnie
(This used to be commit b0da25cb79f860bfa14ba7a8419c7996d936292b)
|
|
existing ctdb_call() mechanism isn't sufficient. The main problem is
that the operations on the record need to be done with a lock held
while a local posix file operation is happening. We can't use a
ctdb_call callback function to do the actual file opens, renames,
unlinks etc as the callback would run on the wrong node.
So this commit adds the prototypes for two new ctdb API functions
which will make a opendb backend easier. Volker will probably
recognise these functions as they are basically the same as what he
did in his earlier Samba clustering code :-)
(This used to be commit d9a997fd390e4162c015435d1c703fb3a4978f2f)
|
|
ctdb backend to use the updated multi-database API
(This used to be commit 44dcac9e4d81bfc078512248967b6240db9d1bd8)
|
|
(This used to be commit 7cf9d07c88b0c81777bb9363d445ac657982a366)
|
|
- merge ctdb_get_num_nodes() from bzr tree
(This used to be commit 3df7527aedeba7ce2f4a6ca2d3b7167f58c6b68a)
|
|
should now work on a real cluster, and not just a localhost simulator
(This used to be commit f05072ad74fb08fd906bc500c5e89930bcc3387f)
|
|
advantage of the ctdb messaging layer for their own data
(This used to be commit b288ba05e5dc2aa5c8cd26eaee1c41b12e4996da)
|
|
handling messages to remote nodes. Implemented dummy functions in the
'local' cluster backend for the messaging hooks, and modified the
messaging layer to check if the destination is remote and redirect
messages via the cluster layer
(This used to be commit 4474552e8fb73efebef32ad8480d7fe9a1e379ef)
|
|
complex once we have code for changing the number of nodes)
- fixed a ctdb/tcp bug in the handling of multiple packets waiting on
a socket
(This used to be commit faf9a1146cb5f33228a11e01b66cb3cbe18bd05d)
|
|
(This used to be commit 2d6e082e813e18dcd43bc8d9a8f445f77e0a8452)
|
|
locks retry immediately when another blocking lock is removed.
(This used to be commit 169920a5341392e84d5b5fb5f39c2b9d5243bb3b)
|
|
rather than allocating a reply_data field each time, I have changed
the ctdb_call API to include a status code. That greatly simplifies
use of the API.
(This used to be commit 70c3acaf8876fa5712e2135df234fe3bc1e32e77)
|
|
- convert brlock code to new API
(This used to be commit cf317480cb715dbaab87c06f824a1db14b09b298)
|
|
standalone and built-in ctdb
(This used to be commit 3e5f29bddfd83914eeec706367b2b1bd30aba31e)
|
|
(This used to be commit 8b5d7d66c91d2bee971373f7da05d1641c556cbc)
|
|
survives very long random locktest runs.
(This used to be commit 53fd66340abd6f637acd4feb7c23c046df110a94)
|
|
couple of hundred opertations. Also removed a lot of the debug code I
was using to track this down.
(This used to be commit 7622e7b4b2694ec14062d0f6de035b946106a6aa)
|
|
reply
(This used to be commit 05d19af38c1e75ba65ed2755c6087df1f937ee2a)
|
|
calculations. It will be interesting to see how portable this is.
The advantage over the sizeof() method is that it avoids padding
problems after the data[1] array. That was causing us to get valgrind
errors.
(This used to be commit fd8e46043903d3650f8f33dcab165800f6869b1d)
|
|
environment for subsystems that have not yet been converted to use
ctdb to get a shared temporary tdb
(This used to be commit 0ed91384497aed6817b2220c31344bfcd45fd033)
|
|
to track down some uninitialised memory (sometimes valgrind gets the
offset wrong, writing to /dev/null 1 byte at a time avoids this)
(This used to be commit 4bf741b567417231c29606904aea2af0a91c941c)
|
|
- this fix looks really ugly but I don't know a better solution...
if we would use uint8_t *data; then we would send the pointer value
also in the network packet and we would need to initialize
s->data = ((void *)(&s->data) + 1;
to make the memcpy statements work as they're currently,
so we use uint8_t data[1] in the struct definition ...
tridge: please review careful!
hopefully fix the build on solaris and HPUX
metze
(This used to be commit 015097677c8a65e9f5a4367f4f89193a4b2de76b)
|
|
metze
(This used to be commit cb59eae91966e3e493c3c992d2b96965d17dac17)
|
|
at the moment the brlock_ctdb backend will sometimes fail after
dmaster migrations. So to pass tests this needs to be set high. Thats
a priority to fix.
(This used to be commit 45f5c272f366f6a793941d97c9522c5b2b0cb639)
|
|
instead of c++ comments
(This used to be commit a3beff12a522a9b9e0088365d8f2740a1785bff5)
|
|
(This used to be commit ba3ce8abe3457a1245fd4746af780c6055d39425)
|
|
it will be interesting to see how the build farm handles this
(This used to be commit 53be449630bd67d649a9e70cc7e25a9799c0616b)
|
|
(This used to be commit 5530e6effe03615499fbdc5ff2fe663ffa0223a9)
|
|
this is in preparation for ctdb
(This used to be commit 489f022175a1022bcca8053116362825daae5e40)
|
|
(This used to be commit 5870830b99a8d76bda1ff5af3fcf8dda9aba50ec)
|
