Bug #47309 ndbd is not restarted after it has been stopped using the kill command
| Submitted: | 14 Sep 2009 12:46 | Modified: | 15 Oct 2009 15:25 |
|---|---|---|---|
| Reporter: | Andrew Morgan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | mysql-5.1-telco-7.0 | OS: | Linux (Fedora 11) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | angel, MySQL Cluster 7.0.6, ndbd | ||
[14 Sep 2009 12:46]
Andrew Morgan
[14 Sep 2009 12:54]
Andrew Morgan
Log files (zipped)
Attachment: data_node_not_restarting.zip (application/x-zip-compressed, text), 48.24 KiB.
[14 Sep 2009 13:52]
Hartmut Holzgraefe
Can't reproduce, a 'simple' "kill" or "kill -15" (SIGTERM) shuts down the data node including the angle process, signals -6 (SIGABRT), -9 (SIGKILL), -11 (SIGSEG) shut down the node and initiate an angel restart: ndb_mgm> Node 3: Forced node shutdown completed, restarting. Initiated by signal 6. Caused by error 6000: 'Error OS signal received(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'. You don't seem to have submitted your config.ini file, but my educated blind guess would be that you don't have set StopOnError=false and so the default behavior kicks in which is to stop a node on errors instead of restarting it? ( http://dev.mysql.md/doc/refman/5.1/en/mysql-cluster-ndbd-definition.html#mysql-cluster-par... )
[14 Sep 2009 15:40]
Andrew Morgan
Hartmut, you were correct about my config - I've retested and it behaves as you'd described. Thanks, Andrew.
[14 Oct 2009 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.