Hi Massimiliano,
When you restart your ndb_mgmd process are you including the --initial option (to force
it to reread config.ini)?
Regards, Andrew.
> -----Original Message-----
> From: Massimiliano Ziccardi [mailto:massimiliano.ziccardi@stripped]
> Sent: 13 September 2010 15:18
> To: Hartmut Holzgraefe
> Cc: cluster@stripped
> Subject: Re: Problem with the NDB database engine
>
> Thank you!!!
> I think that's the problem!!
>
> I don't know why, but the command you gave me gives this output:
> 1000 1000
>
> So, I think it is ignoring the MaxNoOfAttributes I set into the
> configuration file....
>
> I've to admit I'm a newbie about the cluster configuration of MySQL,
> however, this is what I do to change the MaxNoOfAttributes (please tell
> me
> if I miss something!!)
> 1) Stop the ndbd services on both servers
> 2) Stop the ndb_mgmd service on the master server
> 3) Stop both the mysql server services
> 4) change the config.ini file on the master server (I think I should
> change
> something on the nodes too, but could not find any instruction about
> that)
> 5) restart everything
>
> Thanks a lot,
> Massimiliano
>
> On Mon, Sep 13, 2010 at 16:03, Hartmut Holzgraefe <
> hartmut.holzgraefe@stripped> wrote:
>
> > On 09/13/2010 03:27 PM, Massimiliano Ziccardi wrote:
> >
> > 1) How can I know the current MaxNoOfAttributes of mysql? I need
> that to
> >> be
> >> sure that mysql is actually reading my config file
> >>
> >
> > ndb_config -q MaxNoOfAttributes
> >
> > --
> > hartmut
> >
> > --
> > MySQL Cluster Mailing List
> > For list archives: http://lists.mysql.com/cluster
> > To unsubscribe:
> > http://lists.mysql.com/cluster?unsub=1
> >
> >
