Bug #49782 | ndb_mgm client does not report data memory decreased | ||
---|---|---|---|
Submitted: | 17 Dec 2009 20:22 | Modified: | 3 Mar 2010 12:34 |
Reporter: | Andrew Hutchings | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Any |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[17 Dec 2009 20:22]
Andrew Hutchings
[21 Dec 2009 8:40]
Bernd Ocklin
This is a regression.
[2 Mar 2010 13:11]
Magnus Blåudd
Fixed by the patch for BUG#31542, see below test protocol. mysql> use test Database changed mysql> create table t1(a int primary key, b int, c varchar(256)) ENGINE = NDB; Query OK, 0 rows affected (0.45 sec) $> test/tools/hugoFill -d test t1 batch = 512 rowsize = 292 -> rows/commit = 448 ERROR: 827 Out of memory in Ndb Kernel, table data (increase DataMemory) Status: Permanent error, Classification: Insufficient space File: HugoTransactions.cpp (Line: 828) ndb_mgm> Node 2: Data usage increased to 82%(530 32K pages of total 640) Node 1: Data usage increased to 85%(550 32K pages of total 640) Node 2: Data usage increased to 95%(608 32K pages of total 640) Node 1: Data usage increased to 96%(617 32K pages of total 640) Node 2: Data usage increased to 99%(636 32K pages of total 640) Node 1: Data usage increased to 99%(636 32K pages of total 640) mysql> TRUNCATE TABLE t1; Query OK, 0 rows affected (0.39 sec) ndb_mgm> Node 2: Data usage decreased to 3%(24 32K pages of total 640) Node 1: Data usage decreased to 3%(24 32K pages of total 640)
[3 Mar 2010 10:28]
Magnus Blåudd
Fixed by patch for bug#31542 Pushed to 6.3.33, 7.0.14 and 7.1.2-beta
[3 Mar 2010 12:34]
Jon Stephens
Documented in the NDB-6.3.33, 7.0.14, and 7.1.2 changelogs. See BUG#31542 for changelog entry. Closed.