Bug #59352 'stop cluster' timed out in "Clean up part" after succeeded add process test
Submitted: 7 Jan 2011 14:19 Modified: 15 Jan 2011 7:22
Reporter: Geir Green Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1.51 ndb-7.1.9a OS:Linux (rhel)
Assigned to: Assigned Account CPU Architecture:Any
Tags: timeout

[7 Jan 2011 14:19] Geir Green
Description:
In a test case for MCM the following happens:

create cluster --package=mypkg --processhosts=ndb_mgmd@loki24,ndbd@loki25,ndbd@loki26,mysqld@loki24 mycluster
...
start cluster mycluster
...
add process --processhosts=ndb_mgmd@loki25,ndbd@loki25,ndbd@loki25,mysqld@loki25,ndbapi@loki25 --set=MaxNoOfSavedEvents:ndb_mgmd=150,InitialNoOfOpenFiles:ndbd:6=30,InitialNoOfOpenFiles:ndbd:7=30,port:mysqld:8=25005,socket:mysqld:8=/export/home/tmp/jagtmp/ndbdevMCM_Nightly/funcCLIAddProcess_12/run/mysql.sock.2 mycluster
...
start process --added mycluster
...
stop cluster mycluster

This command times out after 5 minutes. It seems to be that the two ndb_mgmds never stop (all other processes have stopped)

This is the first nighttest with version 7.1.9a.

How to repeat:
n/a
[7 Jan 2011 14:29] Geir Green
attatchments to bug report.

Attachment: bug_59352.tar.gz (application/x-gzip, text), 13.86 KiB.

[15 Jan 2011 7:22] Jonas Oreland
this is a duplicate of http://bugs.mysql.com/bug.php?id=59437