Bug #39667 Starting phase is reported differently in cluster.log and ndb_mgm
Submitted: 26 Sep 2008 13:04 Modified: 14 Dec 2008 10:17
Reporter: Oli Sennhauser Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:6.3.17 OS:Any
Assigned to: Guangbao Ni CPU Architecture:Any

[26 Sep 2008 13:04] Oli Sennhauser
Description:
Cluster start phase 3 is already reported as completed but with ndb_mgm still shows in phase 3...

How to repeat:
fill up a cluster with a lot of data and do a restart.

Fri Sep 26 14:58:37 CEST 2008
mysql@laptop:~/cluster/5.1.27-ndb-6.3.17 [mysqld51276317, 3315]> ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> all status
Connected to Management Server at: localhost:1186
Node 10: starting (Phase 3) (mysql-5.1.27 ndb-6.3.17)

2008-09-26 14:55:40 [MgmSrvr] INFO     -- Node 1: Node 10 Connected
2008-09-26 14:55:40 [MgmSrvr] INFO     -- Node 10: Start phase 2 completed (system restart)
2008-09-26 14:55:41 [MgmSrvr] INFO     -- Node 10: Start phase 3 completed (system restart)
2008-09-26 14:55:47 [MgmSrvr] INFO     -- Node 10: DICT: index 6 activated done

Suggested fix:
Bring these infos in sync. if 3 is completed I asume we are in phase 4...
[23 Oct 2008 10:11] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/56872

2721 Guangbao Ni	2008-10-23
      BUG#39667 Starting phase is reported differently in cluster.log and ndb_mgm
[4 Nov 2008 10:26] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/57761

2722 Guangbao Ni	2008-11-04
      BUG#39667 Starting phase is reported differently in cluster.log and ndb_mgm
[3 Dec 2008 5:56] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/60454

2760 Guangbao Ni	2008-12-03
      BUG#39667 Starting phase is reported differently in cluster.log and ndb_mgm
[3 Dec 2008 6:19] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/60457

2778 Guangbao Ni	2008-12-03 [merge]
      BUG#39667 Starting phase is reported differently in cluster.log and ndb_mgm
[3 Dec 2008 6:21] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/60458

3154 Guangbao Ni	2008-12-03 [merge]
      BUG#39667 Starting phase is reported differently in cluster.log and ndb_mgm
[3 Dec 2008 6:25] Bugs System
Pushed into 5.1.30-ndb-6.2.17  (revid:gni@mysql.com-20081203134939-yjzst7wolvi4mjx2) (version source revid:gni@mysql.com-20081203134939-yjzst7wolvi4mjx2) (pib:5)
[3 Dec 2008 6:39] Bugs System
Pushed into 5.1.30-ndb-6.3.20  (revid:gni@mysql.com-20081203141223-glo9qvagqwz7fzv3) (version source revid:gni@mysql.com-20081203141223-glo9qvagqwz7fzv3) (pib:5)
[3 Dec 2008 6:42] Bugs System
Pushed into 5.1.30-ndb-6.4.0  (revid:gni@mysql.com-20081203141438-cufmumc6aois0kqg) (version source revid:gni@mysql.com-20081203141438-cufmumc6aois0kqg) (pib:5)
[3 Dec 2008 6:54] Guangbao Ni
pushed into telco-6.2 
and merged into telco-6.3 and telco-6.4
[3 Dec 2008 7:03] Guangbao Ni
pushed into telco-6.2 
and merged into telco-6.3 and telco-6.4
[12 Dec 2008 23:28] Bugs System
Pushed into 6.0.9-alpha  (revid:gni@mysql.com-20081203134939-yjzst7wolvi4mjx2) (version source revid:tomas.ulin@sun.com-20081209185954-9svcixh2p5hsfi6w) (pib:5)
[14 Dec 2008 10:17] Jon Stephens
Documented in the ndb-6.2.17 and ndb-6.3.20 changelogs as follows:

        Start phase reporting was inconsistent between the management client and
        the cluster logs.