In the mysql documentation (http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-ndbd-definition.html for 5.1 or http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-ndbd-definition.html for 5.5, chapter "Defining MySQL Cluster Data Nodes"), I read the following :
Currently, MySQL Cluster can use a maximum of 512 MB for hash indexes per partition, which means in some cases it is possible to get Table is full errors in MySQL client applications even when ndb_mgm -e "ALL REPORT MEMORYUSAGE" shows significant free DataMemory.
I am currently using mysql 5.1.44 ndbcluster 7.1.4
Using the command all report memoryusage (in ndb_mgm tool) in my cluster, I see that index usage is 825 Mo, and I don't see any error.
Could someone explain what does that mean ? Is there really a limitation on Index Memory Usage ?
ndb_mgm> all report memoryusage
Node 4: Data usage is 91%(314029 32K pages of total 344320)
Node 4: Index usage is 83%(106561 8K pages of total 128032)
Node 3: Data usage is 91%(314029 32K pages of total 344320)
Node 3: Index usage is 83%(106561 8K pages of total 128032)
Node 3: Data usage is 91%(314029 32K pages of total 344320)
Node 3: Index usage is 83%(106561 8K pages of total 128032)
Node 4: Data usage is 91%(314029 32K pages of total 344320)
Node 4: Index usage is 83%(106561 8K pages of total 128032)
Node 5: Data usage is 91%(314467 32K pages of total 344320)
Node 5: Index usage is 83%(107278 8K pages of total 128032)
Node 6: Data usage is 91%(314467 32K pages of total 344320)
Node 6: Index usage is 83%(107278 8K pages of total 128032)
Node 4: Data usage is 91%(314029 32K pages of total 344320)
Node 4: Index usage is 83%(106561 8K pages of total 128032)
Node 5: Data usage is 91%(314467 32K pages of total 344320)
Node 5: Index usage is 83%(107278 8K pages of total 128032)
Node 6: Data usage is 91%(314467 32K pages of total 344320)
Node 6: Index usage is 83%(107278 8K pages of total 128032)
Thanks.
Currently, MySQL Cluster can use a maximum of 512 MB for hash indexes per partition, which means in some cases it is possible to get Table is full errors in MySQL client applications even when ndb_mgm -e "ALL REPORT MEMORYUSAGE" shows significant free DataMemory.
I am currently using mysql 5.1.44 ndbcluster 7.1.4
Using the command all report memoryusage (in ndb_mgm tool) in my cluster, I see that index usage is 825 Mo, and I don't see any error.
Could someone explain what does that mean ? Is there really a limitation on Index Memory Usage ?
ndb_mgm> all report memoryusage
Node 4: Data usage is 91%(314029 32K pages of total 344320)
Node 4: Index usage is 83%(106561 8K pages of total 128032)
Node 3: Data usage is 91%(314029 32K pages of total 344320)
Node 3: Index usage is 83%(106561 8K pages of total 128032)
Node 3: Data usage is 91%(314029 32K pages of total 344320)
Node 3: Index usage is 83%(106561 8K pages of total 128032)
Node 4: Data usage is 91%(314029 32K pages of total 344320)
Node 4: Index usage is 83%(106561 8K pages of total 128032)
Node 5: Data usage is 91%(314467 32K pages of total 344320)
Node 5: Index usage is 83%(107278 8K pages of total 128032)
Node 6: Data usage is 91%(314467 32K pages of total 344320)
Node 6: Index usage is 83%(107278 8K pages of total 128032)
Node 4: Data usage is 91%(314029 32K pages of total 344320)
Node 4: Index usage is 83%(106561 8K pages of total 128032)
Node 5: Data usage is 91%(314467 32K pages of total 344320)
Node 5: Index usage is 83%(107278 8K pages of total 128032)
Node 6: Data usage is 91%(314467 32K pages of total 344320)
Node 6: Index usage is 83%(107278 8K pages of total 128032)
Thanks.