Bug #54341 Two new settings related to StopOnError=0

• Submitted: 8 Jun 2010 14:51
• Modified: 19 Aug 2010 8:59
• Reporter: Andrew Hutchings
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S4 (Feature request)
• Version: mysql-5.1-telco-7.0
• OS: Any
• Assigned to: Frazer Clement
• CPU Architecture: Any

[8 Jun 2010 14:51] Andrew Hutchings

Description:
MySQL Cluster's StopOnError=0 currently has no way to set the restart delay or number of retries.  This feature request is to add settings for this.

How to repeat:
.

[16 Aug 2010 12:20] 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/115777

3122 Frazer Clement	2010-08-16
      Bug#54341 Two new settings related to StopOnError=0
      
      Two new datanode settings are created :
        - MaxStartFailRetries (Default 3)
          This is the maximum number of consecutive times that an Ndbd Angel 
          process will restart an Ndbd Worker process that failed to startup.
          The default value is 3, after which the Angel will exit.
          Setting this to 0 results in infinite retries.
        - StartFailRetryDelay (Default 0)
          This is the delay in seconds after the Ndbd Angel process detects that
          the Ndbd worker has failed during startup, before it attempts to 
          start the Ndbd worker again.
      
      These settings only take effect when StopOnError=0.

[16 Aug 2010 12: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/115784

3122 Frazer Clement	2010-08-16
      Bug#54341 Two new settings related to StopOnError=0
      
      Two new datanode settings are created :
        - MaxStartFailRetries (Default 3)
          This is the maximum number of consecutive times that an Ndbd Angel 
          process will restart an Ndbd Worker process that failed to startup.
          The default value is 3, after which the Angel will exit.
          Setting this to 0 results in infinite retries.
        - StartFailRetryDelay (Default 0)
          This is the delay in seconds after the Ndbd Angel process detects that
          the Ndbd worker has failed during startup, before it attempts to 
          start the Ndbd worker again.
      
      These settings only take effect when StopOnError=0.

[16 Aug 2010 13:41] Bugs System

Pushed into mysql-5.1-telco-7.0 5.1.47-ndb-7.0.18 (revid:[e-mail]-20100816132531-ham912s03rw4ypa0) (version source revid:[e-mail]-20100816132531-ham912s03rw4ypa0) (merge vers: 5.1.47-ndb-7.0.18) (pib:20)

[16 Aug 2010 13:45] Bugs System

Pushed into mysql-5.1-telco-6.2 5.1.47-ndb-6.2.19 (revid:[e-mail]-20100816124926-9v6r6h30o8b4gko7) (version source revid:[e-mail]-20100816124926-9v6r6h30o8b4gko7) (merge vers: 5.1.47-ndb-6.2.19) (pib:20)

[16 Aug 2010 13:48] Bugs System

Pushed into mysql-5.1-telco-6.3 5.1.47-ndb-6.3.37 (revid:[e-mail]-20100816130130-5oy6afk6jeue4o44) (version source revid:[e-mail]-20100816130130-5oy6afk6jeue4o44) (merge vers: 5.1.47-ndb-6.3.37) (pib:20)

[16 Aug 2010 13:50] Frazer Clement

Also pushed to 7.1.7

[19 Aug 2010 8:59] Jon Stephens

Documented in the NDB-6.2.19, 6.3.37, 7.0.18, and 7.1.7 changelogs, as follows:

        More finely-grained control over restart-on-failure behavior is
        provided with two new data node configuration parameters
        MaxStartFailRetries and StartFailRetryDelay. MaxStartFailRetries
        limits the total number of retries made before giving up on 
        starting the data node; StartFailRetryDelay sets the number of 
        seconds between retry attempts. 

        These parameters are used only if StopOnError is set to 0.

Also added descriptions of new parameters to "Defining Data Nodes" section and summary tables in Manual.

Closed.