| Bug #18118 | Master node shutdown caused full cluster crash | ||
|---|---|---|---|
| Submitted: | 9 Mar 2006 22:21 | Modified: | 27 Mar 2006 13:30 | 
| Reporter: | Adam Dixon (Candidate Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) | 
| Version: | 4.1, 5.0, 5.1 | OS: | Linux (RHEL4) | 
| Assigned to: | Jonas Oreland | CPU Architecture: | Any | 
   [9 Mar 2006 22:21]
   Adam Dixon        
  
 
   [17 Mar 2006 10:25]
   Jonas Oreland        
  The problem is that the master takeover prints so much in cluster log so that sendbuffer gets full... solution: timeslice or decrease printouts
   [21 Mar 2006 14:15]
   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/3993
   [24 Mar 2006 12:32]
   Jonas Oreland        
  pushed into 5.1.8
   [24 Mar 2006 15: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/4125
   [27 Mar 2006 10:13]
   Jonas Oreland        
  pushed into 5.0.20
   [27 Mar 2006 12:05]
   Jonas Oreland        
  pushed into 4.1.19
   [27 Mar 2006 13:30]
   Jon Stephens        
  Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html
Additional info:
Documented bugfix in 4.1.19, 5.0.20, 5.1.8 changelogs. Closed.
 