Rechercher dans le manuel MySQL
ndb_waiter repeatedly (each 100 milliseconds)
prints out the status of all cluster data nodes until either the
cluster reaches a given status or the
--timeout
limit is exceeded,
then exits. By default, it waits for the cluster to achieve
STARTED
status, in which all nodes have
started and connected to the cluster. This can be overridden
using the --no-contact
and
--not-started
options.
The node states reported by this utility are as follows:
NO_CONTACT
: The node cannot be contacted.UNKNOWN
: The node can be contacted, but its status is not yet known. Usually, this means that the node has received aSTART
orRESTART
command from the management server, but has not yet acted on it.NOT_STARTED
: The node has stopped, but remains in contact with the cluster. This is seen when restarting the node using the management client'sRESTART
command.STARTING
: The node's ndbd process has started, but the node has not yet joined the cluster.STARTED
: The node is operational, and has joined the cluster.SHUTTING_DOWN
: The node is shutting down.SINGLE USER MODE
: This is shown for all cluster data nodes when the cluster is in single user mode.
The following table includes options that are specific to the NDB Cluster native backup restoration program ndb_waiter. Additional descriptions follow the table. For options common to most NDB Cluster programs (including ndb_waiter), see Section 22.4.31, “Options Common to NDB Cluster Programs — Options Common to NDB Cluster Programs”.
Table 22.359 Command-line options for the ndb_waiter program
Format | Description | Added, Deprecated, or Removed |
---|---|---|
Wait for cluster to reach NO CONTACT state | All NDB 8.0 releases |
|
Wait for cluster to reach NOT STARTED state | All NDB 8.0 releases |
|
Wait for cluster to enter single user mode | All NDB 8.0 releases |
|
Wait this many seconds, then exit whether or not cluster has reached desired state; default is 2 minutes (120 seconds) | All NDB 8.0 releases |
|
List of nodes not to be waited for. | All NDB 8.0 releases |
|
List of nodes to be waited for. | All NDB 8.0 releases |
Usage
ndb_waiter [-c connection_string]
Additional Options
Instead of waiting for the
STARTED
state, ndb_waiter continues running until the cluster reachesNO_CONTACT
status before exiting.Instead of waiting for the
STARTED
state, ndb_waiter continues running until the cluster reachesNOT_STARTED
status before exiting.Time to wait. The program exits if the desired state is not achieved within this number of seconds. The default is 120 seconds (1200 reporting cycles).
The program waits for the cluster to enter single user mode.
When this option is used, ndb_waiter does not wait for the nodes whose IDs are listed. The list is comma-delimited; ranges can be indicated by dashes, as shown here:
shell> ndb_waiter --nowait-nodes=1,3,7-9
ImportantDo not use this option together with the
--wait-nodes
option.When this option is used, ndb_waiter waits only for the nodes whose IDs are listed. The list is comma-delimited; ranges can be indicated by dashes, as shown here:
shell> ndb_waiter --wait-nodes=2,4-6,10
ImportantDo not use this option together with the
--nowait-nodes
option.
Sample Output.
Shown here is the output from ndb_waiter
when run against a 4-node cluster in which two nodes have been
shut down and then started again manually. Duplicate reports
(indicated by ...
) are omitted.
shell> ./ndb_waiter -c localhost
Connecting to mgmsrv at (localhost)
State node 1 STARTED
State node 2 NO_CONTACT
State node 3 STARTED
State node 4 NO_CONTACT
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 UNKNOWN
State node 3 STARTED
State node 4 NO_CONTACT
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTING
State node 3 STARTED
State node 4 NO_CONTACT
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTING
State node 3 STARTED
State node 4 UNKNOWN
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTING
State node 3 STARTED
State node 4 STARTING
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTED
State node 3 STARTED
State node 4 STARTING
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTED
State node 3 STARTED
State node 4 STARTED
Waiting for cluster enter state STARTED
NDBT_ProgramExit: 0 - OK
If no connection string is specified, then
ndb_waiter tries to connect to a management
on localhost
, and reports
Connecting to mgmsrv at (null)
.
Nederlandse vertaling
U hebt gevraagd om deze site in het Nederlands te bezoeken. Voor nu wordt alleen de interface vertaald, maar nog niet alle inhoud.Als je me wilt helpen met vertalingen, is je bijdrage welkom. Het enige dat u hoeft te doen, is u op de site registreren en mij een bericht sturen waarin u wordt gevraagd om u toe te voegen aan de groep vertalers, zodat u de gewenste pagina's kunt vertalen. Een link onderaan elke vertaalde pagina geeft aan dat u de vertaler bent en heeft een link naar uw profiel.
Bij voorbaat dank.
Document heeft de 26/06/2006 gemaakt, de laatste keer de 26/10/2018 gewijzigd
Bron van het afgedrukte document:https://www.gaudry.be/nl/mysql-rf-mysql-cluster-programs-ndb-waiter.html
De infobrol is een persoonlijke site waarvan de inhoud uitsluitend mijn verantwoordelijkheid is. De tekst is beschikbaar onder CreativeCommons-licentie (BY-NC-SA). Meer info op de gebruiksvoorwaarden en de auteur.
Referenties
Deze verwijzingen en links verwijzen naar documenten die geraadpleegd zijn tijdens het schrijven van deze pagina, of die aanvullende informatie kunnen geven, maar de auteurs van deze bronnen kunnen niet verantwoordelijk worden gehouden voor de inhoud van deze pagina.
De auteur Deze site is als enige verantwoordelijk voor de manier waarop de verschillende concepten, en de vrijheden die met de referentiewerken worden genomen, hier worden gepresenteerd. Vergeet niet dat u meerdere broninformatie moet doorgeven om het risico op fouten te verkleinen.