- 23 Mar, 2007 17 commits
-
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
test case
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-telco-gca-single-user
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-single-user
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-telco-gca-single-user
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@poseidon.mysql.com authored
into poseidon.mysql.com:/home/tomas/mysql-5.0-ndb
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
stewart@willster.(none) authored
-
- 22 Mar, 2007 23 commits
-
-
stewart@willster.(none) authored
into willster.(none):/home/stewart/Documents/MySQL/5.1/ndb-work
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-telco-gca
-
tomas@whalegate.ndb.mysql.com authored
- make sure all extra flags are reset
-
stewart@mysql.com[stewart] authored
Turns out I broke it. Index: ndb-work/storage/ndb/src/mgmsrv/MgmtSrvr.cpp ===================================================================
-
stewart@mysql.com[stewart] authored
Turns out they can be useful in working out what's going wrong. Index: ndb-work/storage/ndb/test/src/NdbRestarter.cpp ===================================================================
-
stewart@mysql.com[stewart] authored
Index: ndb-work/storage/ndb/src/mgmapi/ndb_logevent.cpp ===================================================================
-
stewart@mysql.com[stewart] authored
[PATCH] WL#3704 mgmapi timeouts: For mgm server, have timeout per operation, not for entire connection (i.e. fix the bug) for TransporterRegistry, keep connection to management server alive. Index: ndb-work/storage/ndb/include/util/InputStream.hpp ===================================================================
-
stewart@mysql.com[stewart] authored
Index: ndb-work/storage/ndb/include/util/InputStream.hpp ===================================================================
-
stewart@mysql.com[stewart] authored
Index: ndb-work/storage/ndb/test/run-test/daily-basic-tests.txt ===================================================================
-
stewart@mysql.com[stewart] authored
Default timout of 30secs for ConfigRetriever Default timout of 5sec for use by Transporter (ports etc). And Ndb_cluster_connection::set_timeout() api for setting timeout from NDBAPI applications. Should be called before connect. e.g. c.set_timeout(4200); c.connect(); Index: ndb-work/storage/ndb/include/mgmcommon/ConfigRetriever.hpp ===================================================================
-
stewart@mysql.com[stewart] authored
as side effect - turbo accellerator patch for ndb_mgm - sholud make it quicker... so that 4mhz cpu will seem even faster. Index: ndb-work/storage/ndb/src/mgmclient/CommandInterpreter.cpp ===================================================================
-
stewart@mysql.com[stewart] authored
use portable method, getting milliseconds between calls - Linux would let us do funky stuff by getting the timeout from select(2). Everywhere else sucks and doesn't let us do that :( Index: ndb-work/storage/ndb/include/util/InputStream.hpp ===================================================================
-
stewart@mysql.com[stewart] authored
Index: ndb-work/storage/ndb/include/mgmapi/mgmapi.h ===================================================================
-
stewart@mysql.com[stewart] authored
Only one timeout value is needed. Also saves 8bytes per NdbMgmHandle :) Index: ndb-work/storage/ndb/include/mgmapi/mgmapi.h ===================================================================
-
stewart@mysql.com[stewart] authored
Index: ndb-work/storage/ndb/test/ndbapi/testMgm.cpp ===================================================================
-
stewart@mysql.com[stewart] authored
Index: ndb-work/storage/ndb/src/mgmsrv/MgmtSrvr.cpp ===================================================================
-
stewart@mysql.com[stewart] authored
Also add an ERROR_codes.txt file for mgmd Index: ndb-work/storage/ndb/src/mgmsrv/ERROR_codes.txt ===================================================================
-
stewart@mysql.com[stewart] authored
In ndb_mgm_call, add checks for expired timeout in (Input|Output)Stream. In case of timeout, we set NdbMgmHandle->last_error and return NULL. In api calls not using ndb_mgm_call (or using it in conjunction with own IO), they'll need to check for timeouts manually. Macros are provided to do this. Add ndb_mgm_disconnect_quiet(h) to disconnect without checking errors (so we don't clobber NdbMgmHandle->last_error). This helps us provide the *consistent* semantic that on timeout we leave the NdbMgmHandle *disconnected*. We check for this in testMgm. Change CHECK_REPLY in mgmapi to also check for set error in handle->last_error This will pick up the ETIMEDOUT errors and return them to client (through returning correct failure code for API call and setting NdbMgmHandle error). Applications written to MGMAPI before this patch will behave as before, and even hopefully check get_last_error and report the error back to the end user! Adding the last CHECK_TIMEDOUT_RET and delete in ndb_mgm_call() we slightly change behaviour of mgmapi. Previously, if disconnect midway through a reply, where there were only optional parameters left, we'd get a Properties object from ndb_mgm_call() containing NULLs for the optional parameters, leading to interesting error messages. This enables the returning of the *real* message and actually improves the API without breaking compatibility. ndb_mgm_start_signallog ndb_mgm_stop_signallog ndb_mgm_log_signals ndb_mgm_set_trace ndb_mgm_insert_error ndb_mgm_set_int64_parameter [1] ndb_mgm_set_string_parameter [1] ndb_mgm_purge_stale_sessions [2] - return error code on error during ndb_mgm_call TODO: ndb_mgm_report_event [2] [1] marked for removal, unused. [2] return codes incorrect in CHECK_HANDLE/CONNECTED. undocumented. Server side: in Services (per session) add macro for injecting timeout error (just waiting 10 seconds before continuing... it does work!) We inject these errors in a number of critical places - including the tricky api functions that don't just use ndb_mgm_call but do their own thing (get_config, get_status and friends) ATRT: Expand testMgm to add timout tests for API. Fully automated. *THEORETICALLY* timing dependent - an ultra-slow network will cause problems and "fake" failures... I welcome other solutions. Tests aren't exhaustive, but cover the generics and the tricky bits. Also test some calling semantics (incl disconnected on error). It is encouraged to add *more* mgmapi tests, not less :) InputStream: Fix where timedout error is set Index: ndb-work/storage/ndb/src/mgmapi/mgmapi.cpp ===================================================================
-