Re: While changing engine to ndbcluster there is an error The Table is Full

[Mikael Ronström]

Hi,

Şükrü ÖZDEMİR Wrote:
-------------------------------------------------------
> Hi
> I have got 2 NDB(8G Ram, 250GB HDD), 2 API(8G Ram,
> 40 GB HDD), 2 MGMT(4 GB RAM, 40 GB HDD) nodes.
>
> There is a database called "ozd" it has 343
> tables.
>
> I have changed 48 tables engine to ndbcluster with
> phpmyadmin, but now I can not change the others.
>
> When I try to change engine, I am facing with an
> error and it says " #1114 - The table
> '#sql-471_87f' is full " but there is nothing in
> it.

This table is a temporary table created while performing
an ALTER TABLE.

Table full here simply means that you run out of
DataMemory.

So the first 47 tables filled the DataMemory.

Your config has only 3GB of DataMemory, you probably
need a lot more than that. You can probably decrease the
IndexMemory.

So problem you are facing is simply not enough memory
to alter all tables. Remember that MySQL Cluster stores
columns in memory by default (There is an option to store
non-index columns on disk, so adding STORAGE DISK to the
ALTER TABLE can put more of the data on disk.

Rgrds Mikael


>
> For exp. There is a tabble called "A" and engine
> is "ndbcluster", and one more table called "B" and
> engine is "innoDB".
>
> It is like reached the max or someting like that I
> cannot change the B to the ndbcluster but if a
> change A's engine to innoDB this time I can change
> B's engine to ndbcluster.
>
> Here is my CONF
>
> MGMT :
>
> [ndbd default]
> # Options affecting ndbd processes on all data
> nodes:
> NoOfReplicas=2 # Number of replicas
> DataMemory=3G # How much memory to allocate for
> data storage
> IndexMemory=2G # How much memory to allocate for
> index storage
> # For DataMemory and
> IndexMemory, we have used the
> # default values. Since the
> "world" database takes up
> # only about 500KB, this should
> be more than enough for
> # this example Cluster setup.
>
> [tcp default]
> # TCP/IP options:
> portnumber=2202 # This the default; however, you
> can use any
> # port that is free for all the
> hosts in the cluster
> # Note: It is recommended that
> you do not specify the port
> # number at all and simply allow
> the default value to be used
> # instead
>
> [ndb_mgmd]
> # Management process options:
> hostname=10.2.2.57 # Hostname or IP
> address of MGM node
> datadir=/var/lib/mysql-cluster # Directory for
> MGM node log files
>
> [ndb_mgmd]
> # Management process options:
> hostname=10.2.2.58 # Hostname or IP
> address of MGM node
> datadir=/var/lib/mysql-cluster # Directory for
> MGM node log files
>
>
> [ndbd]
> # Options for data node "A":
> # (one [ndbd]
> section per data node)
> hostname=10.2.2.60 # Hostname or IP
> address
> datadir=/usr/local/mysql/data # Directory for
> this data node's data files
>
> [ndbd]
> # Options for data node "B":
> hostname=10.2.2.61 # Hostname or IP
> address
> datadir=/usr/local/mysql/data # Directory for
> this data node's data files
>
> [mysqld]
> # SQL node options:
> hostname=10.2.2.53 # Hostname or IP
> address
> # (additional
> mysqld connections can be
> # specified for
> this node for various
> # purposes such as
> running ndb_restore)
> [mysqld]
> # SQL node options:
> hostname=10.2.2.54 # Hostname or IP
> address
> # (additional
> mysqld connections can be
> # specified for
> this node for various
> # purposes such as
> running ndb_restore)
>
>
> API and NDB CONF : my.cnf
>
> [mysqld]
> # Options for mysqld process:
> ndbcluster
> federated # run NDB storage
> engine
>
> [mysql_cluster]
> # Options for MySQL Cluster processes:
> ndb-connectstring=10.2.2.57,10.2.2.58 # location
> of management server