Bug #75527 | Forced node shutdown completed...Initiated by signal 11. | ||
---|---|---|---|
Submitted: | 16 Jan 2015 11:49 | Modified: | 22 Jul 2016 13:12 |
Reporter: | Marek Knappe | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
Version: | mysql-5.6.21 ndb-7.3.7 | OS: | Linux (CentOS 5.8) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | ndb;signal 11;crash;mysq;node shutdown |
[16 Jan 2015 11:49]
Marek Knappe
[16 Jan 2015 12:08]
Marek Knappe
I would like to add also that on this cluster we are unable to perform any backup which is also critical for us: ndb_mgm> START BACKUP WAIT COMPLETED Connected to Management Server at: localhost:1186 Waiting for completed, this may take several minutes Node 2: Backup 11 started from 1 has been aborted. Error: 4237 Backup failed * 3001: Could not start backup * Too many triggers: Permanent error: Application error
[17 Mar 2015 11:19]
Marek Knappe
Hi Umesh, Any progress on this?
[1 Jun 2015 8:51]
MySQL Verification Team
Sorry, I'm not able to reproduce this issue at my end. I'll check internally if this has been fixed recently in 7.3.9 builds and then I would update you this.
[21 Jul 2015 12:40]
Marek Knappe
Thanks for Info. Looking forward for more news.
[22 Jul 2016 13:12]
MySQL Verification Team
Hi, reviewing this bug after some time passed. I cannot reproduce this on - 7.0.37 - 7.1.34 - 7.3.13 - 7.4.11 Did you upgraded your system maybe recently and did you encountered this same bug on the new release? I'm unable to grab your log from dropbox so if you did encounter this same error on one of the releases I can't reproduce it on please upload the full logs again kind regards Bogdan Kecman