| Bug #19275 | Lot of DDL ops lead to 773: Out of string memory Permanent error: Schema error | ||
|---|---|---|---|
| Submitted: | 22 Apr 2006 13:56 | Modified: | 28 Jun 2006 3:58 |
| Reporter: | Jonathan Miller | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.1.10 | OS: | Linux (Linux 32 Bit OS) |
| Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[22 Apr 2006 13:56]
Jonathan Miller
[22 Apr 2006 13:58]
Jonathan Miller
correction: -> Why has some of the memory been released by now? should read -> Why hasn't some of the memory been released by now?
[21 Jun 2006 14:01]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/8027
[21 Jun 2006 14:14]
Jonas Oreland
pushed into 5.1-new-ndb
documentation of bug: it was a memleak in alter table
documentation of "StringMemory" (in [NDBD DEFAULT] or [NDBD])
specifies how much memory is allocated for strings (e.g table names etc...)
if value specified is [0-100] it means % of max needed
if > 100 it means actual bytes.
default value is 5%
(4.1 & 5.0 used 100%, i.e. over allocated by ~95%)
[27 Jun 2006 22:03]
Tomas Ulin
pushed to 5.1.12
[28 Jun 2006 3:58]
Jon Stephens
Documented bugfix in 5.1.12 changelog. Added StringMemory info to data node definition seciton of Cluster chapter in 4.1/5.0/5.1 Manual. Closed.
