restart

Note: restart can't be run if start, stop, backup, restore, publish-config, or reshape-nodes is currently running.

To restart components, run the following from the Admin Server:

./bdd-admin.sh restart [option <arg>]

restart supports the following options.

Option	Description
`-t, --timeout <minutes>`	The amount of time to wait (in minutes) before terminating the component(s). If this value is 0, the script forces the component(s) to shut down immediately. If it's greater than 0, the script waits the specified amount of time for the component(s) to shut down gracefully, then terminates them if they don't. If this option isn't specified, the script shuts the component(s) down gracefully, which may take a very long time. If a component is down, a timeout value should be specified or the script will hang.
`-c, --component <component(s)>`	A comma-separated list of the components to restart: `agent`: Dgraph HDFS Agent `dgraph`: Dgraph `dp`: Hive Table Detector cron job `bddServer`: Studio and Dgraph Gateway `transform`: Transform Service `clustering`: Clustering Service (if enabled) `wm`: Workflow Manager Service Note the following: Restarting `bddServer` requires the WebLogic Server username and password if the `BDD_WLS_USERNAME` and `BDD_WLS_PASSWORD` environment variables aren't set. `agent` can't be restarted if ZooKeeper isn't running.
`-n, --node <hostname(s)>`	A comma-separated list of the nodes to run on. Each must be defined in $BDD_HOME/BDD_manager/conf/bdd.conf.

Option

Description

-t, --timeout <minutes>

The amount of time to wait (in minutes) before terminating the component(s).

If this value is 0, the script forces the component(s) to shut down immediately. If it's greater than 0, the script waits the specified amount of time for the component(s) to shut down gracefully, then terminates them if they don't.

If this option isn't specified, the script shuts the component(s) down gracefully, which may take a very long time. If a component is down, a timeout value should be specified or the script will hang.

-c, --component <component(s)>

A comma-separated list of the components to restart:

agent: Dgraph HDFS Agent
dgraph: Dgraph
dp: Hive Table Detector cron job
bddServer: Studio and Dgraph Gateway
transform: Transform Service
clustering: Clustering Service (if enabled)
wm: Workflow Manager Service

Note the following:

Restarting bddServer requires the WebLogic Server username and password if the BDD_WLS_USERNAME and BDD_WLS_PASSWORD environment variables aren't set.
agent can't be restarted if ZooKeeper isn't running.

-n, --node <hostname(s)>

A comma-separated list of the nodes to run on. Each must be defined in $BDD_HOME/BDD_manager/conf/bdd.conf.

If no options are specified, the script restarts all supported components gracefully.

Restarting Data Processing

Running restart on the dp and wm components has different effects on Data Processing:

Running it on dp disables and reenables the Hive Table Detector cron job.
Running it on wm cancels all current Data Processing jobs, and stops and restarts the Workflow Manager Service. If a timeout value is included, the script waits for the specified amount of time before canceling current jobs; otherwise, it waits for them to complete normally, which may take a long time.

Be aware that when the Workflow Manager Service is restarted, no new Data Processing jobs can run until it's up again.

Examples

The following command gracefully shuts down and then restarts all supported components:

./bdd-admin.sh restart

The following command waits 5 minutes for the Dgraph and the HDFS Agent on the web009.us.example.com node to shut down gracefully, terminates it if it's still running, then restarts it:

./bdd-admin.sh restart -t 5 -c dgraph -n web009.us.example.com