- 6.5 MySQL Cluster Start Phases
- 6.5.1 Initialization Phase (Phase -1)
- 6.5.2 Configuration Read Phase (STTOR Phase -1)
- 6.5.3 STTOR Phase 0
- 6.5.4 STTOR Phase 1
- 6.5.5 STTOR Phase 2
- 6.5.6 NDB_STTOR Phase 1
- 6.5.7 STTOR Phase 3
- 6.5.8 NDB_STTOR Phase 2
- 6.5.9 STTOR Phase 4
- 6.5.10 NDB_STTOR Phase 3
- 6.5.11 STTOR Phase 5
- 6.5.12 NDB_STTOR Phase 4
- 6.5.13 NDB_STTOR Phase 5
- 6.5.14 NDB_STTOR Phase 6
- 6.5.15 STTOR Phase 6
- 6.5.16 STTOR Phase 7
- 6.5.17 STTOR Phase 8
- 6.5.18 NDB_STTOR Phase 7
- 6.5.19 STTOR Phase 9
- 6.5.20 STTOR Phase 101
- 6.5.21 System Restart Handling in Phase 4
- 6.5.22 START_MEREQ Handling
The first step in handling START_MEREQ is to
ensure that no local checkpoint is currently taking place;
otherwise, it is necessary to wait until it is completed. The
next step is to copy all distribution information from the
master DBDIH to the starting
DBDIH. After this, all metadata is
synchronized in DBDICT (see
Section 6.5.21, “System Restart Handling in Phase 4”).
After blocking local checkpoints, and then synchronizing distribution information and metadata information, global checkpoints are blocked.
The next step is to integrate the starting node in the global checkpoint protocol, local checkpoint protocol, and all other distributed protocols. As part of this the node status is also updated.
After completing this step the global checkpoint protocol is
permitted to start again, the START_MECONF
signal is sent to indicate to the starting node that the next
phase may proceed.
