MySQL Bugs: #61428: ndbd --initial-start

Bug #61428	ndbd --initial-start
Submitted:	6 Jun 2011 22:49	Modified:	9 Jul 2011 12:11
Reporter:	burak baskan	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	MySQL distrib mysql-5.1.56 ndb-7.1.13, f	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
when I try to restart the node # 2 with initial parameter, management server produces the following error message;

Node 2: Forced node shutdown completed. Occured during startphase 2. Caused by error 2307: 'Partitioned cluster detected. Please check if cluster is already running(Arbitration error). Temporary error, restart node'.

How to repeat:
shut the node server from management interface and switch to the the node server shell;

[root@c1 ~]# ndbd --initial-start
2011-06-06 17:18:58 [ndbd] INFO     -- Angel connected to '10.28.35.8:1186'
2011-06-06 17:18:58 [ndbd] INFO     -- Angel allocated nodeid: 2
[root@c1 ~]#

ndb_error_reporter file

Attachment: ndb_error_report_20110606174044.tar.bz2 (application/x-download, text), 100.01 KiB.

Also it seems I can not re-set DataMemory size. Here is my config;

[ndbd default]
NoOfReplicas=2
DataMemory=6G
IndexMemory=2G
MaxNoOfAttributes=3500
MaxNoOfOrderedIndexes=4096
MaxNoOfUniqueHashIndexes=3000
NoOfFragmentLogFiles=90
MaxNoOfTables=1500
MaxNoOfConcurrentOperations=1000000
MaxNoOfLocalOperations=1100000
[ndb_mgmd]
hostname=10.28.35.8
datadir=/var/lib/mysql-cluster
[ndbd]
hostname=10.28.35.12
datadir=/usr/local/mysql/data
[ndbd]
hostname=10.28.35.10
datadir=/usr/local/mysql/data
[mysqld]
hostname=10.28.35.2

This is the warning message I get;
Node 2: Data usage increased to 96%(2481 32K pages of total 2560)

and script to start ndb_mgmd;
ndb_mgmd --initial -f /var/lib/mysql-cluster/config.ini --configdir=/var
/lib/mysql-cluster/ --ndb-nodeid=1

even if the command output looks fine;
[root@s1 ~]# ndb_config --type ndbd -q Id,DataMemory -r '\n'
2,83886080
3,83886080
[root@s1 ~]#

Thank you for the report.

I see in mdb_mgmd log Node 3 was restarted afer it started with --initial-start:

2011-06-06 17:02:35 [MgmtSrvr] INFO     -- Node 3: Node shutdown initiated
2011-06-06 17:02:43 [MgmtSrvr] INFO     -- Node 3: Suma: initiate handover for shutdown with nodes 0000000000000004 GCI: 13401
2011-06-06 17:02:43 [MgmtSrvr] INFO     -- Node 3: Suma: handover to node 2 gci: 13401 buckets: 00000002 (2)
2011-06-06 17:02:49 [MgmtSrvr] INFO     -- Node 3: Suma: handover complete
2011-06-06 17:02:50 [MgmtSrvr] INFO     -- Node 3: Node shutdown completed, restarting, no start.

Can it be so Node 3 is running without --initial-start parameter?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".