T,
When I connect to ndb_mgmd with ndn_mgm and run SHOW
I see no nodes connected.
NDB> show
Cluster Configuration
---------------------
2 NDB Node(s)
DB node: 1 (not connected)
DB node: 2 (not connected)
1 MGM Node(s)
MGM node: 3 (Version: 3.5.0)
4 API Node(s)
API node: 4 (not connected)
API node: 5 (not connected)
API node: 6 (not connected)
API node: 7 (not connected)
> The error message you get indicates that there is
> already a node up and running with node id 6 or that
> nodeid 6 of the correct
> type.
Question 1:
Does type refer to DB, MGM, or API?
Question 2:
In previous versions of the Cluster, node IDs were
assigned by placing an "ID: N" directive in
config.ini. Right? Now it appears that IDs are just
assigned based
on the order in which they appear in config.ini.
Question 3:
Also in previous versions, the MGM node's config.ini
and Ndb.cfg were placed inside a nodeID-specific
directory. Now this no longer seems to be the case.
Correct?
Question 4:
Same question about the directory structure on remote
computers. In previous versions of the Cluster
software we used nodeID-specific directories for the
configurations and NDB filesystems. Is this no longer
required? Deprecated? Wrong? Please advise.
Has anyone else had trouble migrating their
multi-node clusters from mysql-4.1.3 to mysql-4.1.5
or is it just me? ;))
BR/
Douglas
--- tulin@stripped wrote:
>
> Douglas,
>
> Sorry for the inconvenience of the config param name
> changes. I hope you fill
> find the changes we've made to be to the better.
>
> On you error message:
>
> In 4.1.3 there was no check that two nodes if there
> were 2 nodes connecting with
> the same nodeid (would typically make the nodes hang
> indefinitely...). Now
> there is such a check. The error message you get
> indicates that there is
> already a node up and running with node id 6 or that
> nodeid 6 of the correct
> type. Please run "ndb_mgm" and the command "show",
> this will indicate which
> nodes are already connected, and what nodeid's are
> available for which
> nodetype. When looking at you config file below it
> looks like your ndbd/DB
> nodes should have id's 1 and 2, and hence you should
> have nodeid=1 or 2 in your
> connectstring.
>
> Note: with 4.1.5 you can also leave out nodeid in
> your connectstring and the
> mysqld should get a free available nodeid. Note
> also that there is a command
> line option for the connectstring to the mysqld that
> you then can use either on
> the command line:
> mysqld --ndbcluster --ndb-connectstring=bush:2200
> or as I personally would prefer in my.cnf:
> [mysqld]
> ndbcluster
> ndb-connectstring=bush:2200
>
> BR,
>
> T
>
> Quoting RadeonFlashBox <radeonflashbox@stripped>:
>
> > I just upgraded from
> mysql-4.1.3-beta-nightly-20040721
> > to mysql-4.1.5-gamma-nightly-20040902. Now I can't
> get
> > my 4-computer cluster up and running.
> >
> > I see the config.ini parameters have changed (e.g.
> > ByteOrder is deprecated, Discless became
> Diskless).
> > Are all changes and new usages explained anywhere?
> >
> > When I try to start up nodes, they (apparently)
> > connect but are not allocated a node id by the
> > ndb_mgmd. Here is the message in the local
> > ndb_0_error.log.
> >
> > <...>
> > Date/Time: Tuesday 7 September 2004 - 10:26:47
> > Type of error: error
> > Message: Invalid Configuration fetched from
> Management
> > Server
> > Fault ID: 2350
> > Problem data: Unable to alloc node id
> > Object of reference: Could not alloc node id: no
> free
> > nodeid 6 for nodetype 0
> > ProgramName: NDB Kernel
> > ProcessID: 22726
> > TraceFile: /var/ndbcluster/ndb/ndb_0_trace.log.1
> > ***EOM***
> > <...>
> >
> > Here my current config.ini:
> >
> > <...>
> >
> > [DB DEFAULT]
> > NoOfReplicas: 2
> > MaxNoOfConcurrentOperations: 10000
> > DataMemory: 40M
> > IndexMemory: 12M
> > Diskless: 0
> > TimeBetweenWatchDogCheck: 30000
> > #FileSystemPath:
> > /var/ndbcluster/mysql-test/ndbcluster-2200
> > FileSystemPath: /usr/local/mysql/ndb
> >
> > [COMPUTER]
> > Id: 1
> > Hostname: bush
> >
> > [COMPUTER]
> > Id: 2
> > HostName: 10.0.1.211
> >
> > [COMPUTER]
> > Id: 3
> > Hostname: 10.0.1.212
> >
> > [COMPUTER]
> > Id: 4
> > Hostname: 10.0.1.213
> >
> > [COMPUTER]
> > Id: 5
> > Hostname: 10.0.1.214
> >
> > [DB]
> > ExecuteOnComputer: 2
> >
> > [DB]
> > ExecuteOnComputer: 3
> >
> > [MGM]
> > PortNumber: 2200
> >
> > [MYSQLD]
> >
> > [MYSQLD]
> >
> > [MYSQLD]
> >
> > [MYSQLD]
> >
> > [TCP DEFAULT]
> > PortNumber: 2202
> > <...>
> >
> > Here's my connect string from a db_node (running
> on
> > another computer):
> >
> > nodeid=6;host=bush:2200
> >
> > BTW I've already tried using an IP address instead
> of
> > hostname in config.ini for [COMPUTER] with ID: 1
> >
> > And I've used an IP address instead of hostname in
> > connect strings.
> >
> > Prior to the upgrade the cluster had been running
> for
> > weeks. Thanks for any help you might provide.
> >
> > BR/
> >
> > Douglas
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Address AutoComplete - You start. We
> finish.
> > http://promotions.yahoo.com/new_mail
> >
> > --
> > MySQL Cluster Mailing List
> > For list archives: http://lists.mysql.com/cluster
> > To unsubscribe:
> http://lists.mysql.com/cluster?unsub=1
> >
> >
>
>
>
>
>
----------------------------------------------------------------
> This message was sent using IMP, the Internet
> Messaging Program.
>
__________________________________
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now.
http://messenger.yahoo.com
