Tags: logicalclocks/rondb
Tags
Merge pull request #117 from mronstro/22.01 RONDB-113: Failure to allocate more than 2 Gbyte of memory in one all…
Merge pull request #113 from mronstro/22.01 Merge fixes into 22.01.0
Merge pull request #112 from mronstro/21.04 Merge fixes into 21.04.3
Bug#20538279 MYSQL IGNORING REPLICATION USERS PASSWORD OPTION AFTER R… …ESTART When the server starts, status vars acquire their values from the option file without invoking the associated check and update functions. The recovery password relies on these functions to set its value without turning the it visible to the user relying on a dummy internal var that never changes its value. As a solution, when the server starts and the plugin is being initialized, we use the dummy password to fetch the value that should not be there, cleaning its value afterwards.
Bug #18875137 NDB : NDB_RESTORE STILL MISSING SOME TYPE CONVERSIONS Add support for ndb_restore to promote text to text columns.
Bug #18496153 EXCESSIVE PHASE 101 DURATION (OR STUCK IN PHASE 101) New diagnostic logging controlled by new environment variable NDB_PATCH both for kernel and ndbapi applications. Also added memory barriers in transporter layer that could possible fix bug. To enable the complete patch in run-time start process with NDB_PATCH=-1 If bug can be reproduced, send logs for analysis. If bug can not be reproduced, retry but turn of new memory barriers For logging and read memory barriers use: NDB_PATCH=3 For logging and write memory barriers use: NDB_PATCH=5 For logging without new memory barriers use: NDB_PATCH=1 With this patch one can also add extra destinations for logs. For syslog add ';syslog' to NDB_PATCH. Example, export NDB_PATCH='-1;syslog' For file add ';file=/path/to/process-specific.file' to NDB_PATCH. Example, export NDB_PATCH='-1;file=/data/mysqld.1.patchlog'
Bug #18599198 Fix by adding timeout for start phase 101
PreviousNext