Bug #9892 Index activation file during node recovery

Submitted:	14 Apr 2005 8:46	Modified:	25 Apr 2005 11:05
Reporter:	Johan Andersson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	5.0.3	OS:	2.4.21-20 (64-bit)
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
Following the nodefailure in Dbacc  (bug 9891), the ordered indexes fail to be activated:

2005-04-14 03:12:31 [MgmSrvr] INFO     -- Node 7: Receive arbitrator node 1 [ticket=6e8a00023ca837da]
2005-04-14 03:13:17 [MgmSrvr] INFO     -- Node 2: Start phase 3 completed (initial node restart)
2005-04-14 03:14:13 [MgmSrvr] INFO     -- Node 2: Start phase 4 completed (initial node restart)
2005-04-14 03:14:14 [MgmSrvr] WARNING  -- Node 2: DICT: index 3 activation failed: code=702 line=0
2005-04-14 03:14:14 [MgmSrvr] WARNING  -- Node 2: DICT: index 5 activation failed: code=702 line=0
2005-04-14 03:20:54 [MgmSrvr] INFO     -- Node 4: Local checkpoint 124 started. Keep GCI = 35885 oldest restorable GCI = 15119

Index 3 belongs to the table (see table def in 9891) stored in one database,
and Index 5 belongs to exactly the same table, but stored in another db

How to repeat:
?

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/internals/24103

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/internals/24104

Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.