Hi Tomas,
I am currently working on a proper fix for this problem. A quick
workaround is to increase the
the parameter
TimeBetweenWatchDogCheck: 30000
which means 30000 ms = 30 seconds. This should allow you to be able to
continue. There are
a number of things possible to improve this matter that I am working
with and will push some fixes
to this week.
Rgrds Mikael
2004-08-04 kl. 15.01 skrev Tomas Kaminskas:
> Hi all,
>
> I am tetsing MySQL cluster (1 computer, 1 mgm node, 1 db node, 1 api
> node).
> Mgm server starting ok:
> NDB Cluster Management Server. Version 3.5.0 (beta)
> Id: 1, Command port: 11000, Statistics port: 0
> Checking all status:
> NDB> all status
> Node 2: No contact
> Then I trying to start db node with -n switch:
> 2004-08-04 15:47:26 [NDB] INFO -- Angel pid: 2974 ndb pid: 2976
> 2004-08-04 15:47:26 [NDB] INFO -- NDB Cluster -- DB node 2
> 2004-08-04 15:47:26 [NDB] INFO -- Version 3.5.0 (beta) --
> Then typing all start from mgmtsrvr:
> NDB> all start
> Executing START on node: 2
> On db node I get such output:
> 2004-08-04 15:47:57 [NDB] INFO -- Start initiated (version 3.5.0)
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Ndb kernel is stuck in: Job Handling
> Shutdown initiated
> Shutdown completed - exiting
> 2004-08-04 15:49:12 [NDB] INFO -- Angel shutting down
>
> If more information is needed I can send my configuration files and
> trace
> files.
>
> Brgds,
> Tomas Kaminskas
>
>
> --
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe:
> http://lists.mysql.com/cluster?unsub=1
>
>
Mikael Ronström, Senior Software Architect
MySQL AB, www.mysql.com
Clustering:
http://www.infoworld.com/article/04/04/14/HNmysqlcluster_1.html
http://www.eweek.com/article2/0,1759,1567546,00.asp
