List:Cluster« Previous MessageNext Message »
From:lonetwin Date:November 20 2009 12:55pm
Subject:Re: errno 136 while importing db in ndbcluster
View as plain text  
Jon,

I ran ndb_size.pl on the same database ( when its just a standalone db
server and not part of any cluster) and the file i got is this :

Parameter Default 4.1 5.0 5.1
DataMemory (KB) 81920 2402976* 2402976* 782528*
NoOfOrderedIndexes 128 1018* 1018* 1018*
NoOfTables 128 1045* 1045* 1045*
IndexMemory (KB) 18432 234936* 50680* 50680*
NoOfUniqueHashIndexes 64 642* 642* 642*
NoOfAttributes 1000 3500* 3500* 3500*
NoOfTriggers 768 7124* 7124* 7124*

The output says NoOfOrderedIndexes should be =1018, and in my config file i
have given 3000.

ndbd default]
DataDir=/var/lib/mysql-cluster
NoOfReplicas=2
LockPagesInMainMemory=1
DataMemory=3000M
IndexMemory=1024M
FragmentLogFileSize=256M
NoOfFragmentLogFiles=12
RedoBuffer=32M
MaxNoOfTables=4096
MaxNoOfAttributes=24756
MaxNoOfOrderedIndexes=3000
MaxNoOfUniqueHashIndexes=1250
MaxNoOfConcurrentOperations=100000


I am also following up this issue on the mysql forum, here :
http://forums.mysql.com/read.php?25,291548,291548

and still nothing seems to be working.

~Sarang

On Fri, Nov 20, 2009 at 5:25 PM, Jon Stephens <jon.stephens@stripped> wrote:

> lonetwin wrote:
>
>> The statement is :
>>
>> DROP TABLE IF EXISTS `location`;
>> /*!40101 SET @saved_cs_client     = @@character_set_client */;
>> /*!40101 SET character_set_client = utf8 */;
>> CREATE TABLE `location` (
>>  `LOCATION_ID` int(11) NOT NULL auto_increment,
>>  `GUI_LOCATION_ID` int(11) default NULL,
>>  `NETWORK_LOCATION_ID` int(11) default NULL,
>>  `SITE_ID` int(11) default NULL,
>>  PRIMARY KEY  (`LOCATION_ID`),
>>  KEY `FK9FF58FB5B3804BD5` (`NETWORK_LOCATION_ID`),
>>  KEY `FK9FF58FB5EC1F206F` (`GUI_LOCATION_ID`),
>>  KEY `FK9FF58FB55EF6DEDD` (`SITE_ID`)
>> ) ENGINE=NDBCLUSTER DEFAULT CHARSET=latin1;
>>
>
> What's you MaxNoOfOrderedIndexes setting in config.ini? You might try
> increasing it.
>
> See
>
> http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-maxnooforderedindexesfor
> info about this parameter.
>
> cheers
>
> jon.
>
>
>
>> On Fri, Nov 20, 2009 at 3:32 PM, Jon Stephens <jon.stephens@stripped>
>> wrote:
>>
>>  lonetwin wrote:
>>>
>>>  Jon,
>>>>
>>>> what exactly do you mean when you ask "definition" of the table ? Am
>>>> sorry,
>>>> i dont quite understand it.
>>>>
>>>>  What was the CREATE TABLE statement used to create the 'location'
>>> table?
>>>
>>>
>>>
>>>  Thanks,
>>>> Sarang
>>>>
>>>> On Fri, Nov 20, 2009 at 2:19 PM, Jon Stephens
> <jon.stephens@stripped>
>>>> wrote:
>>>>
>>>>  lonetwin wrote:
>>>>
>>>>>  Hello Everyone,
>>>>>
>>>>>> I have a mysql database , i used mysqldump to take a backup of
> this
>>>>>> database, and all of it got saved to a file : backup.sql
>>>>>> Here the default engine was INNODB. This file i wanted to import
> into
>>>>>> my
>>>>>> mysql cluster. So i changed the engine name in the file from
> INNODB to
>>>>>> NDBCLUSTER.
>>>>>> Now this backup.sql i am trying to import into my cluster setup.
>>>>>>
>>>>>> My setup is a 3 machine setup, with two servers acting as
> data/mysql
>>>>>> node
>>>>>> and 1 server acting as the management node.
>>>>>>
>>>>>>  From the data node , i am using the following command to import
> the
>>>>>> backup.sql file
>>>>>>
>>>>>> # mysql -uroot -ppass test < backup.sql
>>>>>>
>>>>>> This operation starts and give error after a while saying :
>>>>>> ERROR 1005 (HY000) at line 3853: Can't create table
> test.location
>>>>>> (errno
>>>>>> 136)
>>>>>>
>>>>>>  Hi!
>>>>>>
>>>>> jon@grindval:~/bin/mysql-5.1/bin> ./perror 136
>>>>> MySQL error code 136: No more room in index file
>>>>>
>>>>> What's the definition of the 'location' table?
>>>>>
>>>>> cheers
>>>>>
>>>>> jon.
>>>>>
>>>>>
>>>>>
>>>>>  My management node shows :
>>>>>
>>>>>> ndb_mgm> ALL REPORT MEMORY
>>>>>>
>>>>>> Node 2: Data usage is 16%(412 32K pages of total 2560)
>>>>>> Node 2: Index usage is 9%(225 8K pages of total 2336)
>>>>>> Node 3: Data usage is 15%(408 32K pages of total 2560)
>>>>>> Node 3: Index usage is 9%(225 8K pages of total 2336)
>>>>>>
>>>>>>
>>>>>>
>>>>>> # ndb_config --type ndbd -q
>>>>>> Id,MaxNoOfOrderedIndexes,MaxNoOfUniqueHashIndexes -r '\n'
>>>>>>
>>>>>> 2,128,64
>>>>>> 3,128,64
>>>>>>
>>>>>>
>>>>>> and
>>>>>>
>>>>>> [root@localhost ~]# ndb_show_tables | grep -c OrderedIndex
>>>>>> 0
>>>>>>
>>>>>> However once i started importing the mysql file into my cluster
> from
>>>>>> the
>>>>>> data node, running the below command on my management node gives
> this
>>>>>> :
>>>>>>
>>>>>> [root@localhost ~]# ndb_show_tables | grep -c OrderedIndex
>>>>>> 8
>>>>>>
>>>>>>
>>>>>> After all this, i am still unable to import the mysql backup file
> into
>>>>>> my
>>>>>> cluster. Any clue how i can get the database into my cluster ?
>>>>>>
>>>>>> Thanks,
>>>>>> Sarang
>>>>>>
>>>>>>
>>>>>>  --
>>>>>>
>>>>>
>>>>> Jon Stephens - jon.stephens@stripped
>>>>> Technical Writer
>>>>> MySQL Documentation Team
>>>>> Sun Microsystems AB
>>>>> MySQL and Software Infrastructure Group
>>>>> Liljeholmen (Stockholm), Sweden
>>>>> Summer: UTC +02.00 / Winter: UTC +01.00
>>>>> Mobile: +46 (0) 736 773 993
>>>>> Skype: plastic-fish
>>>>> MySQL: www.mysql.com
>>>>> Sun: www.sun.com
>>>>>
>>>>>
>>>>>
>>>>>  --
>>>
>>>
>>> Jon Stephens - jon.stephens@stripped
>>> Technical Writer
>>> MySQL Documentation Team
>>> Sun Microsystems AB
>>> MySQL and Software Infrastructure Group
>>> Liljeholmen (Stockholm), Sweden
>>> Summer: UTC +02.00 / Winter: UTC +01.00
>>> Mobile: +46 (0) 736 773 993
>>> Skype: plastic-fish
>>> MySQL: www.mysql.com
>>> Sun: www.sun.com
>>>
>>>
>>>
>>
>
> --
>
>
> Jon Stephens - jon.stephens@stripped
> Technical Writer
> MySQL Documentation Team
> Sun Microsystems AB
> MySQL and Software Infrastructure Group
> Liljeholmen (Stockholm), Sweden
> Summer: UTC +02.00 / Winter: UTC +01.00
> Mobile: +46 (0) 736 773 993
> Skype: plastic-fish
> MySQL: www.mysql.com
> Sun: www.sun.com
>
>

Thread
errno 136 while importing db in ndbclusterlonetwin20 Nov
  • Re: errno 136 while importing db in ndbclusterGeert Vanderkelen20 Nov
    • Re: errno 136 while importing db in ndbclusterlonetwin20 Nov
  • Re: errno 136 while importing db in ndbclusterJon Stephens20 Nov
    • Re: errno 136 while importing db in ndbclusterlonetwin20 Nov
      • Re: errno 136 while importing db in ndbclusterJon Stephens20 Nov
        • Re: errno 136 while importing db in ndbclusterlonetwin20 Nov
          • Re: errno 136 while importing db in ndbclusterJon Stephens20 Nov
            • Re: errno 136 while importing db in ndbclusterlonetwin20 Nov
              • Re: errno 136 while importing db in ndbclusterJon Stephens21 Nov
                • Re: errno 136 while importing db in ndbclusterlonetwin21 Nov
                  • Re: errno 136 while importing db in ndbclusterJohan Andersson23 Nov