Bug #6328 | Cluster API node crashes, and cannot reenter cluster without restarting MGM node | ||
---|---|---|---|
Submitted: | 29 Oct 2004 16:32 | Modified: | 10 Nov 2004 13:55 |
Reporter: | Russell Glaue | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 4.1.7 | OS: | Linux (Red Hat Enterprise 3) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[29 Oct 2004 16:32]
Russell Glaue
[29 Oct 2004 16:33]
Russell Glaue
Cluster API node crashes, and cannot reenter cluster without restarting MGM node
[10 Nov 2004 13:55]
Tomas Ulin
What we believe is the problem is that when a node dies in this manner some sockets are not closed. This leads the management server to believe that this node is still making use of that node id. We don't have a great solution to this at this point (for 4.1). so the options that are there right now are as stated before: 1. restart the management server to reset this (erroneous) state 2. once you've figured out your nodeids and decided on a config, run the management server with --no-nodeid-checks and specify nodeids in the connectstrings and avoid the issue as a while. and 3. in 4.1.8 we will also offer a new command in the management server: PURGE STALE SESSIONS which fixes the issue without restarting the management server. ndb_mgm> purge stale sessions Purged sessions with node id's: 1 ndb_mgm> purge stale sessions No sessions purged For 5.0 we will redesign the protocol for reserving nodeids to avoid this situation (we want to avoid protocol changes in 4.1).
[13 Mar 2014 13:33]
Omer Barnir
This bug is not scheduled to be fixed at this time.