|
| 1 | +================================================== |
| 2 | +mysql-5.1.X-ndb-6.2.Y |
| 3 | +================================================== |
| 4 | + |
| 5 | +mysql-5.1.19-ndb-6.2.3 (released 2007-07-02) |
| 6 | +(additional bugs fixed compared to mysql-5.1.19) |
| 7 | + |
| 8 | + Bug #29331 Incorrect node killed on GCP Stop (COPY_GCI) |
| 9 | + Bug #29057 Incorrect handling of file 0 during redo execution(Error while reading REDO log) |
| 10 | + Bug #29067 Incorrect order during redo invalidation(Error while reading REDO log) |
| 11 | + Bug #29118 Incorrect handling of loglap in redo invalidation (Error while reading REDO log) |
| 12 | + Bug #29229 memory corruption in dbtup |
| 13 | + Bug #29185 Large IN list crashes mysqld with cluster and condition pushdown |
| 14 | + Bug #29176 drop table can crash pgman |
| 15 | + Bug #28989 hpux11 ps_row warnings |
| 16 | + Bug #25305 rpl_ndb_UUID.test fails on pb-valgrind |
| 17 | + Bug #29167 Insufficient nodes for SR |
| 18 | + Bug #27640 backup id not displayed in the output of "ndb_mgm start backup wait completed" |
| 19 | + Bug #28949 n_mix valgrind failing in pushbuild |
| 20 | + Bug #29099 slow backup for disk data |
| 21 | + Bug #26342 auto_increment_increment AND auto_increment_offset REALLY REALLY anger NDB cluster |
| 22 | + Bug #29103 ndb_restore segfaults on NULL var[char|binary] |
| 23 | + Bug #29074 preserve file timestamps in ndb_error_reporter |
| 24 | + Bug #29073 Store history for ndb_mgm |
| 25 | + Bug #29063 mgmapi: connect timeout set incorrectly |
| 26 | + Bug #29044 blob code sets error code on transaction object |
| 27 | + Bug #28724 for blobs, op flag to not set error on trans |
| 28 | + Bug #28751 Lots of memory locked in memory causes high kswapd |
| 29 | + Bug #28899 not possible to set separate watchdog timeout at startup |
| 30 | + Bug# 28726 LCP files not removed after initial system restart |
| 31 | + Bug #20612 failed ndbrequire in PGMAN |
| 32 | + Bug #28443 transporter gets stuck when >1024 signals received at once |
| 33 | + Bug #28770 file already opened error when corrupt schema file |
| 34 | + Bug #28749 MaxNoOfOpenFiles offset by 1 |
| 35 | + Bug #26783 replication status unknown after cluster or mysqld failure |
| 36 | + Bug #28717 Race between NODE_FAILREP and COPY_GCIREQ |
| 37 | + Bug #28719 multi pk update ignore corrupts data |
| 38 | + Bug #28653 Fast GCP + high load + high RedoBuffer causes ndbrequire |
| 39 | + Bug #28525 Node failures in PGMAN at ndbrequire (line 430) |
| 40 | + |
| 41 | + |
| 42 | +================================================== |
| 43 | +mysql-5.1.15-ndb-6.1.X |
| 44 | +================================================== |
| 45 | + |
| 46 | +mysql-5.1.15-ndb-6.1.16 (not released) |
| 47 | + |
| 48 | + Bug #29331 Incorrect node killed on GCP Stop (COPY_GCI) |
| 49 | + Bug #29057 Incorrect handling of file 0 during redo execution(Error while reading REDO log) |
| 50 | + Bug #29067 Incorrect order during redo invalidation(Error while reading REDO log) |
| 51 | + Bug #29118 Incorrect handling of loglap in redo invalidation (Error while reading REDO log) |
| 52 | + Bug #29176 drop table can crash pgman |
| 53 | + |
| 54 | +mysql-5.1.15-ndb-6.1.15 (2007-06-20) |
| 55 | + |
| 56 | + Bug #29229 memory corruption in dbtup |
| 57 | + |
| 58 | +mysql-5.1.15-ndb-6.1.14 (2007-06-19) |
| 59 | + |
| 60 | + Bug #29176 missing stack pruning in drop_page |
| 61 | + Bug #29167 Insufficient nodes for SR |
| 62 | + |
| 63 | +mysql-5.1.15-ndb-6.1.13 (2007-06-15) |
| 64 | + |
| 65 | + Bug #29099 slow backup for disk data |
| 66 | + |
| 67 | +mysql-5.1.15-ndb-6.1.12 (2007-06-13) |
| 68 | + |
| 69 | + Bug #29044 memory buddy allocator "unoptimal" memory handling |
| 70 | + extend backup dump to give more info |
| 71 | + |
| 72 | +mysql-5.1.15-ndb-6.1.11 (2007-06-06) |
| 73 | + |
| 74 | + Bug #28751 Lots of memory locked in memory causes high kswapd |
| 75 | + Bug #28899 not possible to set separate watchdog timeout at startup |
| 76 | + Bug #28726 LCP files not removed after initial system restart |
| 77 | + Bug #20612 failed ndbrequire in PGMAN |
| 78 | + make size of redo log files (fragment log files) configurable (error 1220) |
| 79 | + |
| 80 | +mysql-5.1.15-ndb-6.1.10 (2007-05-30) |
| 81 | + |
| 82 | + Bug #28783 heartbeat failures under high load |
| 83 | + Bug #28770 file already opened error when corrupt schema file |
| 84 | + Bug #28717 Race between NODE_FAILREP and COPY_GCIREQ |
| 85 | + Bug #28525 Node failures in PGMAN at ndbrequire (line 430) |
| 86 | + Bug #28653 Fast GCP + high load + high RedoBuffer causes ndbrequire |
| 87 | + Bug #28749 MaxNoOfOpenFiles offset by 1 |
| 88 | + Added addditional 'times' printout in ndbd WatchDog thread |
| 89 | + Some filename changes to avoid 'tar' issues with 99 char limit |
| 90 | + Removed some extra printouts in ndbd out file |
| 91 | + |
| 92 | +mysql-5.1.15-ndb-6.1.9 (2007-05-24) |
| 93 | + |
| 94 | + Bug #28593 cluster backup scans in acc index order, bad for disk data |
| 95 | + Bug #28443 transporter gets stuck when >1024 signals received at once |
| 96 | + |
| 97 | +mysql-5.1.15-ndb-6.1.8 (2007-05-18) |
| 98 | + |
| 99 | + Bug #28491 Expand check gets disabled in some cases (initial node restart) |
| 100 | + Bug #28348 Dropped tables not removed from LCP |
| 101 | + Bug #20535 NDB API implicit insert of NULL does not overwrite old value |
| 102 | + Bug #27437 NDB Data node crashes during mysqldump inserts |
| 103 | + Bug #27942 node failure during massive insert |
| 104 | + |
| 105 | +mysql-5.1.15-ndb-6.1.7 (2007-05-05) |
| 106 | + |
| 107 | + Bug #26121 mysqldump includes LOCK TABLES general_log WRITE |
| 108 | + Bug #28161 Detached triggers + DD and only MM update could cause node failure |
| 109 | + Bug #25530 --with-readline fails with commercial source packages |
| 110 | + Bug #25741 AllocNodeIdRef::NodeFailureHandlingNotCompleted |
| 111 | + Bug #27205 Occational 899 if delete+insert during LCP |
| 112 | + Bug #24667 After ALTER TABLE operation ndb_dd table becomes regular ndb |
| 113 | + Bug #28093 ndb: retry sleep in get table stats 30s instead of 30ms |
| 114 | + Bug #28073 Infinite loop in lock queue. |
| 115 | + Bug #27495 Missing implementation of NdbTransaction::executeAsynch(). |
| 116 | + Bug #28023 NR can fail to update GCI |
| 117 | + Bug #27756 Memleak with insert+delete |
| 118 | + Bug #27757 Tup scan cant see own records |
| 119 | + Bug #27748 Inconsistent replication(backup) with some multi-update combinations |
| 120 | + Bug #27651 Very high load can cause event api to get out of sync, "out of order buckets" |
| 121 | + Bug #27728 Partially connected API's can cause problem for SUMA |
| 122 | + Bug #27663 Missmatched free/delete in listObjects |
| 123 | + Bug #27560 Memory usage of mysqld grows while doing nothing |
| 124 | + Bug #27581 Drop/truncate table can result in node/cluster-crash |
| 125 | + |
| 126 | + (no bug number) fix bug in my.cnf config handling, put64 for 64-bit variables |
| 127 | + |
| 128 | + Other changes: |
| 129 | + - Force varpart, such that tables can handle online add column when feature arrives |
| 130 | + |
| 131 | + Test tools update for measuring replication latency: |
| 132 | + |
| 133 | + - new ndb tool 'rep_latency' to measure replication latency |
| 134 | + - simple extend of 'listen_event' to do apply on remote cluster |
| 135 | + |
| 136 | +mysql-5.1.15-ndb-6.1.6 (2007-03-30) |
| 137 | + |
| 138 | + Bug #27529 Slave crashes on lots of updates |
| 139 | + Bug #27512 Inconsistent tuples when using variable size and >16Gb datamemory |
| 140 | + Bug #27378 update becomes delete on slave |
| 141 | + Bug #27466 nf during nr can leave cluster in inconsistent state |
| 142 | + Bug #27444 DataMemory missing from report in cluster logs |
| 143 | + Bug #27044 replicated with unique field ndb table allows duplicate key inserts |
| 144 | + Bug #26286 row-based logging scales worse than statement-based logging |
| 145 | + Bug #19896 Last_Errno: 4294967295, Error in Write_rows event: (error number 4 billion ?) |
| 146 | + Bug #27320 ndb handler does not reset extra flags on reset() |
| 147 | + Bug #27283 Race condition in GCP Master take-over |
| 148 | + Bug #26825 MySQL Server Crashes in high load |
| 149 | + Bug #27286 Rare racecondition in nodeid allocation on master failure |
| 150 | + Bug #27291 Setting LockPagesInMainMemory to zero doesn't work |
| 151 | + Bug #20185 Node failure might cause other node failure |
| 152 | + Bug #27203 ScanDelete+Scan+Insert could cause node crash |
| 153 | + Bug #27169 xtra word sent in SUMA::resend_bucket causing crash of mysqld(event listener) |
| 154 | + Bug #27005 Node failure + API failure can crash SUMA resend |
| 155 | + Bug #27087 Unoptimal handling of failed API in SUMA |
| 156 | + Bug #27102 Node can crash during flush of undo during restart with filesystem error |
| 157 | + Bug #27003 Failure during noderestart could crash/hang alive node (and hence cluster) |
| 158 | + (not reported) correct event buffer status reporting |
| 159 | + |
| 160 | +mysql-5.1.15-ndb-6.1.5 (2007-03-15) |
| 161 | + |
| 162 | + Bug #26997 - mysqld segfault when in single user mode |
| 163 | + Bug #26825 - MySQL Server Crashes in high load |
| 164 | + Bug #25743 - If undo_buffer_size (for LG) greater than the inital shared memory (default 20M), ndbd nodes are crashed |
| 165 | + Bug #26899 - ndb_restore cannot restore selected tables and databases |
| 166 | + Bug #26900 - ndb_restore printout option does not give structured data |
| 167 | + Bug #26720 - Infinite loop on unknown signal in logging function |
| 168 | + |
| 169 | + * ndb_apply_status schema change |
| 170 | + * ndb_restore options for printing to file |
| 171 | + |
| 172 | + Note: since ndb_apply_status schema change this version is not backwards compatible |
| 173 | + |
| 174 | +mysql-5.1.15-ndb-6.1.4 (limited test release) |
| 175 | + |
| 176 | + Bug #26741 - ndb_restore with only print_data seg faults |
| 177 | + Bug #26739 - ndb_restore segfault on some 64-bit architectures |
| 178 | + Bug #26663 - cluster have issues with api nodeids > 63 |
| 179 | + |
| 180 | +mysql-5.1.15-ndb-6.1.3 (25 Feb 2007) |
| 181 | + |
| 182 | + Bug #26515 - Incorrect pointer after FSCLOSECONF in REDO invalidation |
| 183 | + Bug #26514 - Invalid memory access could occur during DD usage |
| 184 | + Bug #26490 - duplicate cluster error code |
| 185 | + Bug #26487 - Bug in extent/page allocation when *using* >1gb datafiles |
| 186 | + Bug #25801 - Internal error if starting partially with missing REDO |
| 187 | + Bug #26481 - Node failure during initial node restart, can lead to subsequent node failures |
| 188 | + Bug #26457 - Incorrect handling of LCP take-over during multi-master-node-failure |
| 189 | + Bug #26454 - LockPagesInMemory=1 is called after distributed communcation has started |
| 190 | + Bug #25239 - Out of memory problem can cause crash in SUMA |
| 191 | + Bug #21033 - Error 0 in readAutoIncrementValue() |
| 192 | + Bug #26293 - cluster mgmt node sometimes doesn't receive events from all nodes on restart |
| 193 | + |
| 194 | + * listEvents ndbapi extension |
| 195 | + * Modified ndb_show_tables to also handle Table Events |
| 196 | + * mysqld option --ndb-wait-connected |
| 197 | + * Possibility to disable arbitration by setting arbitrationrank=0 on all nodes |
| 198 | + * All dump 2352 |
| 199 | + * Different READ/SCAN (EX-SH) |
| 200 | + * New dump commands for tracking hanging locks |
| 201 | + * Change level on StartREDOLog to make it default come up in cluster log |
| 202 | + * Make ndbd_redo_log_reader be build default |
| 203 | + |
| 204 | +--------------------------------------------------- |
| 205 | + |
| 206 | +mysql-5.1.16-ndb-6.2.0 (2007-03-09) |
| 207 | + |
| 208 | + * WAN settings for TCP transporters |
| 209 | + * moved initialization of ndbd fs block first to ensure that it gets enough space for allocation of file system thread stacks |
| 210 | + * added listEvents |
| 211 | + * modified ndb_show_tables to also handle Table Events |
| 212 | + * added mysqld option --ndb-wait-connected |
| 213 | + * Add possibility to disable arbitration by setting arbitrationrank=0 on all nodes |
| 214 | + * Add all dump 2352 |
| 215 | + * Add different READ/SCAN (EX-SH) |
| 216 | + * ndb - add new dump commands for tracking hanging locks |
| 217 | + * Change level on StartREDOLog to make it default come up in cluster log |
| 218 | + * Make ndbd_redo_log_reader be build default |
| 219 | + * Integrate mem-manager with TUP removing need for DataMemory2 |
| 220 | + * New interface(ndbapi) for iterating over ndb-object connected to a Ndb_cluster_connection |
| 221 | + * New interface(ndbapi) for starting transaction with hints |
| 222 | + * Different handling of AbortOption in ndbapi |
| 223 | + |
| 224 | +--------------------------------------------------- |
| 225 | + |
| 226 | +mysql-5.1.15-ndb-6.1.2 (7 Feb 2007) |
| 227 | + |
| 228 | + Bug #26267 - using node ids > 48 causes invalid memory access |
| 229 | + |
| 230 | +--------------------------------------------------- |
| 231 | + |
| 232 | +mysql-5.1.15-ndb-6.1.1 (31 Jan 2007) |
| 233 | + |
| 234 | + Bug #25997 - Valgrind reports leak in event code in mysqld during hadeling of NF and CF |
| 235 | + Bug #25794 - Delete+Read (in same op) crashes datanodes if >5 cols or disk/varchar |
| 236 | + Bug #25286 - NDB data node crashed in DBLQH, Line 2483 |
| 237 | + |
| 238 | + (* added extra version info to API to enable support for non-supported online software upgrade) |
| 239 | + * 255 node support |
| 240 | + |
| 241 | + Notes: |
| 242 | + |
| 243 | + - This release is not online upgradable with ndb-6.1.0. |
| 244 | + - All executables needs to be replaced |
| 245 | + - All ndbapi/mgmapi application should be recompiled |
| 246 | + |
| 247 | +--------------------------------------------------- |
| 248 | + |
| 249 | +mysql-5.1.14-ndb-6.1.0 (20 Dec 2006) |
| 250 | + |
| 251 | + Bug #25059 - Unique index lookup execute(Commit) on non existing tuple can lead to 4012 |
| 252 | + Bug #25090 - Incorrect handling of execute(Commit, AO_IgnoreError), can lead to DBCT crash |
| 253 | + Bug #19956 - Problems with VARCHAR primary key and BLOB fields |
| 254 | + Bug #24949 - Pulling cable from _last_ db-node can cause 6min timeout in api |
| 255 | + Bug #25001 - MEDIUMTEXT column not stored on disk |
| 256 | + Bug #24664 - Rare problem in LCP, can lead to unability to restart |
| 257 | + Bug #24917 - Makeing node restart with "newly" dropped disk table can cause failure during restart |
| 258 | + Bug #24914 - Start Transaction with hint guessed incorrectly |
| 259 | + Bug #21948 - Repeated create/drop/truncate(DD) together with restarts can cause SR failure |
| 260 | + Bug #17605 - DD Extents are not available until after LCP |
| 261 | + Bug #22773 - NDB_LE_Connected sent when it should be NDB_LE_Disconnected |
| 262 | + Bug #24166 - SR-crash if DD and hidden key |
| 263 | + |
| 264 | + * add support for periodic mem-reporting, config.ini parameter "MemReportFrequency" which is specified in seconds |
| 265 | + |
0 commit comments