Bug #80650 testNodeRestart -n Bug18612SR T1 fails in startphase 0 by signal 11
Submitted: 7 Mar 2016 22:50 Modified: 11 Mar 2016 12:44
Reporter: Mauritz Sundell Email Updates:
Status: Closed Impact on me:
None 
Category:Tests: Cluster Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[7 Mar 2016 22:50] Mauritz Sundell 
Description:
testNodeRestart -n Bug18612SR T1 fails with data node crash by signal 11 during startphase 0.

This is due to bad merge of patch for Bug#22084822 AUTOTEST TESTNODERESTART -N BUG18612SR SOMETIMES DID NOT CLEAR ERROR.
From 7.4 Dbdih::replicaRecord is replaced with Dbdih::c_replicaRecordPool while Bug#22084822 patch still uses replicaRecord.

2016-03-07 18:07:24 [ndbd] INFO     -- newestRestorableGCI 807
2016-03-07 18:07:24 [ndbd] INFO     -- [1/3] frag 1285, replica 2 @0x128, SYSFILE @0x1779310
2016-03-07 18:07:27 [ndbd] ALERT    -- Node 2: Forced node shutdown completed. Occured during startphase 0. Initiated by signal 11.

How to repeat:
Run testNodeRestart -n Bug18612SR T1 several times.

Suggested fix:
Replace use of Dbdih::replicaRecord with Dbdih::c_replicaRecordPool
[11 Mar 2016 9:28] Mauritz Sundell 
Posted by developer:
 
Pushed to 7.4.11, and, 7.5.2.
Fix bug in test code, no need to document.
[11 Mar 2016 12:44] Jon Stephens 
Fixed in NDB 7.4.11 and 7.5.2. Testing only--no user-facing changes to document. Closed.