Bug #42354 No error details on error 1304 "BackupRef::SequenceFailure"

• Submitted: 26 Jan 2009 19:37
• Modified: 27 Jan 2009 23:17
• Reporter: Hartmut Holzgraefe
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S4 (Feature request)
• Version: mysql-5.1.31 ndb-6.3.21-RC (any?)
• OS: Linux
• Assigned to: Jonas Oreland
• CPU Architecture: Any

[26 Jan 2009 19:37] Hartmut Holzgraefe

Description:
When a cluster backup fails with

  [MgmSrvr] ALERT -- Node x: Backup request from y failed to start. Error: 1304

there is no hint of the actual failure reason anywhere.

The actual problem seems to be the Backup::sendBackupRef() method which is a wrapper around sendSignal(). On signal sending failures it raises an error signal containing an error code defined by the sendBackupRef() call but does not record the actual reason for sendSignal() to fail.

How to repeat:
Check Backup::sendBackupRef() code

Suggested fix:
Add extra error logging in Backup::sendBackupRef() to preserve information on the actual signal sending failure reason.

[27 Jan 2009 14:32] 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/64149

2800 Jonas Oreland	2009-01-27
      ndb - bug#42354 - add retries in case of sequence errors + add info event about which error that occured

[27 Jan 2009 15:05] Bugs System

Pushed into 5.1.31-ndb-6.2.17 (revid:[e-mail]-20090127145543-3h31xza6bpejc2wu) (version source revid:[e-mail]-20090127143231-04uq7hkj2fbxuoxk) (merge vers: 5.1.31-ndb-6.2.17) (pib:6)

[27 Jan 2009 15:06] Bugs System

Pushed into 5.1.31-ndb-6.3.22 (revid:[e-mail]-20090127145937-krvmboln0bpt9ygq) (version source revid:[e-mail]-20090127143944-1ujhjoic0zayvl0d) (merge vers: 5.1.31-ndb-6.3.22) (pib:6)

[27 Jan 2009 15:08] Bugs System

Pushed into 5.1.31-ndb-6.4.2 (revid:[e-mail]-20090127150314-k9cxqznugatfphbq) (version source revid:[e-mail]-20090127145219-5rnijpickcz9rzqj) (merge vers: 5.1.31-ndb-6.4.2) (pib:6)

[27 Jan 2009 23:17] Jon Stephens

Documented bugfix in the NDB-6.2.17, 6.3.22, and 6.4.2 changelogs as follows:

        When a cluster backup failed with Error 1304 (Node
        node_id1: Backup request from node_id2 failed to start), no clear 
        reason for the failure was given.

        As part of this fix, MySQL Cluster now retries backups in the event 
        of sequence errors.

        See also Bug #22698.

[10 Feb 2009 20:13] Bugs System

Pushed into 6.0.10-alpha (revid:[e-mail]-20090210194937-s7xshv5l3m1v7wi9) (version source revid:[e-mail]-20090127161149-9npj9dxe7yw5arca) (merge vers: 6.0.10-alpha) (pib:6)

[25 Jul 2019 6:42] Daoming Han

I got a same problem . version ndb-7.6.10 .It is the latest version . How can i resolve this
problem