| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
(This used to be ctdb commit 1942c21fe7b52f2b0c8f6895bdc7efd70505a9db)
|
| |
| |
| |
| | |
(This used to be ctdb commit b921dc2c7932e0c1ece6ac3f57e117d0500f8214)
|
|/
|
|
| |
(This used to be ctdb commit 025e58ba2b870ebb861b015d5c79dac7f5402bfb)
|
|
|
|
| |
(This used to be ctdb commit 9755f9c62fd14abc65189fc06629f37546f53082)
|
|\
| |
| |
| | |
(This used to be ctdb commit ddf390da2bceb5b3f431433aec424d99d98c05f4)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit 02ec7d6abb75a7c0a414efd4a50d44e6f1e5e407)
|
| |
| |
| |
| | |
(This used to be ctdb commit 9a543968ba0379fbf8e977e184f22f4349d6243f)
|
| |
| |
| |
| | |
(This used to be ctdb commit 0d7a71f35bb8ce95231f8ca1e8e3e4024fe657e5)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 37ef65737571a4290a150c28cf2b0a6b221253fd)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to the database it created (so the client can open and access the same
file)
(This used to be ctdb commit c2eda19499b3263b2248c41bd531fb73c7b42212)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
store the idr as the high 16 bits and use a rotating counter for the low
16 bits.
(This used to be ctdb commit 7c763b7b5e6ca54a6df4586893ddaf1b508b4c22)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
lmaster instead of what the nodes think is the dmaster (which might be
stale) improve performance.
(This used to be ctdb commit f535f79e6a2a6c6d07141b96e0b957fa93c684f4)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 54aaf64cf0681329cdcdc4b7f76e1335952bb683)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit f787f9c966bab82065b979b0a6fcc5c056c7cee4)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 796fdbe8efc3d74515218ddcb25abdbec2e9c2b7)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit ecea04741fe552aa409ab165d7c69ead9649986c)
|
| |
| |
| |
| |
| |
| | |
the lmaster
(This used to be ctdb commit b2599834d2ace7369a1b36f85fdf6eb62f047e30)
|
| |
| |
| |
| | |
(This used to be ctdb commit f2076338221c5cb28f9045ce5345cc6a9b429f1a)
|
| |
| |
| |
| | |
(This used to be ctdb commit 3ddc1e4f1d3660d33cc2a07e53b66772116e9640)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
dmaster request stage, and instead directly send a dmaster
reply. This avoids a race condition where a new call comes in for
the same record while processing the dmaster request
- don't keep any redirect records during a ctdb call. This prevents a
memory leak in case of a redirect storm
(This used to be ctdb commit 59889ca0fd606c7d2156839383a09dfc5a2e4853)
|
| |
| |
| |
| | |
(This used to be ctdb commit 671ed94011e21396571a3f4a5191b9a83911c952)
|
| |
| |
| |
| | |
(This used to be ctdb commit 25f36f7edaa56a16692949d6750b65d74bf4218f)
|
| |
| |
| |
| | |
(This used to be ctdb commit a64c6ace26559b2793f2a804430fb0fc53f03a34)
|
| |
| |
| |
| |
| |
| | |
- add some debug code
(This used to be ctdb commit 26ad1ec3a3b872520a735e4fe4f224f716643731)
|
| |
| |
| |
| | |
(This used to be ctdb commit 23d892c2696c5c1dd9f12f1ccd1acfa264be4fb6)
|
| |
| |
| |
| | |
(This used to be ctdb commit c9959e5741a17fd52070b744714eb00bf92a93eb)
|
| |
| |
| |
| |
| |
| | |
- added lockwait latency
(This used to be ctdb commit 0b5d196147e644cf8b172cb4b593fd46b1caa386)
|
| |
| |
| |
| | |
(This used to be ctdb commit 908d6c6a936e21f70f05827ce302e966cca0132a)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
processed immediately, but the input routines indirectly assumed
they were being called as a new event (for example, a calling
routine might queue the packet, then afterwards modify the ltdb
record). The solution was to make self packets queue via a zero
timeout.
- fixed unlinking of the socket in a exit in the lockwait code. Needed
an _exit instead of exit so atexit() doesn't trigger
- print latency of lockwait delays
(This used to be ctdb commit 1b0684b4f6a976f4c5fe54394ac54d121810b298)
|
| |
| |
| |
| | |
(This used to be ctdb commit 43e4b83fc796b05baccfff6a34df398c821aa018)
|
| |
| |
| |
| |
| |
| | |
reverted my suggestion in debug.c (based on my false error detection)
(This used to be ctdb commit 5c52c9f37639c65b551c10d1706c49653cd99742)
|
| |
| |
| |
| | |
(This used to be ctdb commit e259620d416497fba5ac43a87f3be7b280c21409)
|
| |
| |
| |
| |
| |
| | |
(this change wasn't necessary)
(This used to be ctdb commit 217d996abdafe91c2f51d9d486d95a6607b56285)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit b40d044fc5b057b707a6f5637313c0836981a66e)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 5f51864f837de5fd262d6a41722605789494cb66)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
record
(This used to be ctdb commit 9159434b1eef39b7de58b30626039f1e45a97306)
|
|/ /
| |
| |
| | |
(This used to be ctdb commit 1950d96458238782c3bfd8e41a053c4be8330ef9)
|
| |
| |
| |
| | |
(This used to be ctdb commit 9a30e0fcbdde587cb1f3d854b8f1d22da19d9af4)
|
| |
| |
| |
| |
| |
| |
| | |
- make ctdb capable of alternative connection (like ib) again, solved the fork problem
- do_debug memory overwrite bugfix (occured using ibwrapper_test with wrong address given)
(This used to be ctdb commit da0b84cda26d544f63841dfd770ed7ebad401944)
|
| |\
| |/
|/|
| | |
(This used to be ctdb commit d9046da5219144afe68f5a376243d998e7068ccd)
|
| |
| |
| |
| |
| |
| | |
in memory
(This used to be ctdb commit f7903b00cdc91ae7d7e38b1a38d2b7b663e3a728)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ctdb_ltdb_lock_requeue() and a small wrapper
- use ctdb_ltdb_lock_requeue() to fix a possible hang in
ctdb_reply_dmaster(), where the ctdb_ltdb_store() could hang waiting
for a client. We now requeue the reply_dmaster packet until we have
the lock
(This used to be ctdb commit 97cd7aa09ce3abbb5e3e965c5c81668e0c0133a5)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
CTDB_FLAG_TORTURE, which forces some race conditions to be much more
likely. For example a 20% chance of not getting the lock on the
first try in the daemon
- abstraced the ctdb_ltdb_lock_fetch_requeue() code to allow it to
work with both inter-node packets and client->daemon packets
- fixed a bug left over in ctdb_call from when the client updated the
header on a call reply
- removed CTDB_FLAG_CONNECT_WAIT flag (not needed any more)
(This used to be ctdb commit 7559dcd184666c3853127e3c8f5baef4fea327c4)
|
|\ \
| | |
| | |
| | | |
(This used to be ctdb commit 257af5c31a311217315e07d6a194c3f96c8dfa80)
|
| | |
| | |
| | |
| | |
| | |
| | | |
daemon will sort these out itself before it sends the call of to either the local handler or a remote daemon
(This used to be ctdb commit 9175d49ba1ce2af99907fa227b50d281f85c98ae)
|
|\| |
| | |
| | |
| | |
| | |
| | | |
remove unused bench_incr function in ctdb_bench.c
(This used to be ctdb commit 39424cb13070c9964121b533a9f9ba448ce49d16)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit e834cf18cfc18c9462f0dfff0315b5b6798771f8)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
srcnode and destnode
update ctdbd_test.c to show how to force a migration onto the local node
(This used to be ctdb commit fe313cee4927075be311e28ea106bd5cc035f217)
|
| |\ \
| | | |
| | | |
| | | | |
(This used to be ctdb commit 45081eadb89fdaf8c831e161ae7df816beda934b)
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
(This used to be ctdb commit e9561cfe190af8c0594de7531fbf087730aae60c)
|