We initially didn't but we got this problem at 92 million rows,
After a lot of research we found a post that stated maybe increasing the max rows would
help, however after reading more on max_rows with NDB it was found that it is not used by
NDBcluster engine and ignored? is this true?
However take note, that we require that it hold 600 million rows... challenge..
I will also add my create table syntax to show you what we're doing.
CREATE TABLE `my_ndb_awesome_large_table ` (
`user_id` int(4) NOT NULL,
`description` varchar(50) NOT NULL,
`type` varchar(64) NOT NULL,
`count` int(4) NOT NULL,
`after` int(3) NOT NULL,
`active` int(1) NOT NULL,
`lastactivity` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
) ENGINE=ndbcluster DEFAULT CHARSET=utf8
Any thoughts on what this virtual "level" might be? because as you can see in my last
email have not run out of index / data space?
On 30/09/2010, at 14:59, Jonas Oreland wrote:
> Are you using "maxrows" in your table definition ?
> On 09/30/10 06:15, Karl Kloppenborg wrote:
>> We have setup a MySQL cluster (pretty standard two NDB nodes + two management
>> 2x cluster processing nodes (running the MySQL NDB daemon + MySQL server)
>> - 144GB ram
>> - 8x 300GB SAS - Raid 10
>> - Data-Storage = 135GB Ram
>> - Index-Storage = 5GB RAM
>> However at 92Million rows in a table, it is returning the TableFull error?
>> My config is as follows:
>> [NDBD DEFAULT]
>> [MYSQLD DEFAULT]
>> [NDB_MGMD DEFAULT]
>> [TCP DEFAULT]
>> # Section for the cluster management node
>> ID=1 #LB1 ID is 1
>> HostName=#.#.#.# #PRIVATE IP OF LB1
>> HostName=#.#.#.# #PRIVATE IP OF LB2
>> ID=2 #ID of LB2 is 2
>> # Section for the storage nodes
>> # IP address of the first storage node
>> HostName=#.#.#.# # PRIVATE IP OF DB1
>> # IP address of the second storage node
>> HostName=#.#.#.# #PRIVATE IP OF DB2
>> # one [MYSQLD] per storage node
>> Can anyone please shed some light on this matter?
>> Karl Kloppenborg
>> MySQL Cluster Mailing List
>> For list archives: http://lists.mysql.com/cluster
>> To unsubscribe: http://lists.mysql.com/cluster?unsub=1