PDF (A4) - 40.5Mb
Man Pages (TGZ) - 259.5Kb
Man Pages (Zip) - 366.7Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb
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 achieveSTARTED 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 aSTARTorRESTARTcommand 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'sRESTARTcommand.STARTING: The node'sndbd 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.
Options that can be used withndb_waiter are shown in the following table. Additional descriptions follow the table.
Usage
ndb_waiter [-cconnection_string]Additional Options
Command-Line Format --character-sets-dir=pathDirectory containing character sets.
Command-Line Format --connect-retries=#Type Integer Default Value 12Minimum Value 0Maximum Value 12Number of times to retry connection before giving up.
Command-Line Format --connect-retry-delay=#Type Integer Default Value 5Minimum Value 0Maximum Value 5Number of seconds to wait between attempts to contact management server.
Command-Line Format --connect-string=connection_stringType String Default Value [none]Same as
--ndb-connectstring.Command-Line Format --core-fileWrite core file on error; used in debugging.
Command-Line Format --defaults-extra-file=pathType String Default Value [none]Read given file after global files are read.
Command-Line Format --defaults-file=pathType String Default Value [none]Read default options from given file only.
Command-Line Format --defaults-group-suffix=stringType String Default Value [none]Also read groups with concat(group, suffix).
Command-Line Format --login-path=pathType String Default Value [none]Read given path from login file.
Command-Line Format --no-login-pathsSkips reading options from the login path file.
Command-Line Format --helpDisplay help text and exit.
Command-Line Format --ndb-connectstring=connection_stringType String Default Value [none]Set connection string for connecting tondb_mgmd. Syntax:
[nodeid=. Overrides entries inid;][host=]hostname[:port]NDB_CONNECTSTRINGandmy.cnf.Command-Line Format --ndb-mgm-tls=levelType Enumeration Default Value relaxedValid Values relaxedstrictSets the level of TLS support required to connect to the management server; one of
relaxedorstrict.relaxed(the default) means that a TLS connection is attempted, but success is not required;strictmeans that TLS is required to connect.Command-Line Format --ndb-mgmd-host=connection_stringType String Default Value [none]Same as --
ndb-connectstring.Command-Line Format --ndb-nodeid=#Type Integer Default Value [none]Set node ID for this node, overriding any ID set by
--ndb-connectstring.--ndb-optimized-node-selectionCommand-Line Format --ndb-optimized-node-selectionEnable optimizations for selection of nodes for transactions. Enabled by default; use
--skip-ndb-optimized-node-selectionto disable.Command-Line Format --ndb-tls-search-path=listType Path name Default Value (Unix) $HOME/ndb-tlsDefault Value (Windows) $HOMEDIR/ndb-tlsSpecify a list of directories to search for a CA file. On Unix platforms, the directory names are separated by colons (
:); on Windows systems, the semicolon character (;) is used as the separator. A directory reference may be relative or absolute; it may contain one or more environment variables, each denoted by a prefixed dollar sign ($), and expanded prior to use.Searching begins with the leftmost named directory and proceeds from left to right until a file is found. An empty string denotes an empty search path, which causes all searches to fail. A string consisting of a single dot (
.) indicates that the search path limited to the current working directory.If no search path is supplied, the compiled-in default value is used. This value depends on the platform used: On Windows, this is
\ndb-tls; on other platforms (including Linux), it is$HOME/ndb-tls. This can be overridden by compiling NDB Cluster using-DWITH_NDB_TLS_SEARCH_PATH.--no-contact,-nInstead of waiting for the
STARTEDstate,ndb_waiter continues running until the cluster reachesNO_CONTACTstatus before exiting.Command-Line Format --no-defaultsDo not read default options from any option file other than login file.
Instead of waiting for the
STARTEDstate,ndb_waiter continues running until the cluster reachesNOT_STARTEDstatus before exiting.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:
$> ndb_waiter --nowait-nodes=1,3,7-9ImportantDonot use this option together with the
--wait-nodesoption.Command-Line Format --print-defaultsPrint program argument list and exit.
--timeout=,seconds-tsecondsTime 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.
Command-Line Format --usageDisplay help text and exit; same as
--help.Command-Line Format --verbose=#Type Integer Default Value 2Minimum Value 0Maximum Value 2Controls verbosity level of printout. Possible levels and their effects are listed here:
0: Do not print (return exit code only; see following for exit codes).1: Print final connection status only.2: Print status each time it is checked.This is the same behavior as in versions of NDB Cluster previous to 8.4.
Exit codes returned byndb_waiter are listed here, with their meanings:
0: Success.1: Wait timed out.2: Parameter error, such as an invalid node ID.3: Failed to connect to the management server.
Command-Line Format --versionDisplay version information and exit.
--wait-nodes=,list-wlistWhen 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:
$> ndb_waiter --wait-nodes=2,4-6,10ImportantDonot use this option together with the
--nowait-nodesoption.
Sample Output. Shown here is the output fromndb_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.
$> ./ndb_waiter -c localhostConnecting to mgmsrv at (localhost)State node 1 STARTEDState node 2 NO_CONTACTState node 3 STARTEDState node 4 NO_CONTACTWaiting for cluster enter state STARTED...State node 1 STARTEDState node 2 UNKNOWNState node 3 STARTEDState node 4 NO_CONTACTWaiting for cluster enter state STARTED...State node 1 STARTEDState node 2 STARTINGState node 3 STARTEDState node 4 NO_CONTACTWaiting for cluster enter state STARTED...State node 1 STARTEDState node 2 STARTINGState node 3 STARTEDState node 4 UNKNOWNWaiting for cluster enter state STARTED...State node 1 STARTEDState node 2 STARTINGState node 3 STARTEDState node 4 STARTINGWaiting for cluster enter state STARTED...State node 1 STARTEDState node 2 STARTEDState node 3 STARTEDState node 4 STARTINGWaiting for cluster enter state STARTED...State node 1 STARTEDState node 2 STARTEDState node 3 STARTEDState node 4 STARTEDWaiting for cluster enter state STARTED If no connection string is specified, thenndb_waiter tries to connect to a management onlocalhost, and reportsConnecting to mgmsrv at (null).
PDF (A4) - 40.5Mb
Man Pages (TGZ) - 259.5Kb
Man Pages (Zip) - 366.7Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb