stop

The stop command stops components.

Warning: Never use SIGKILL, kill -9, or any other OS command to stop BDD components. Always use bdd-admin with the stop command. If you need to stop a component immediately, run stop with -t 0.
To stop components, run the following from the Admin Server: 
./bdd-admin.sh stop [option <arg>]
Note: stop can't be run if start, restart, backup, restore, publish-config, or reshape-nodes is currently running.

stop 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.

-c, --component <component(s)> A comma-separated list of the components to stop:
  • 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 that when stop runs on the bddServer component (or all components), it will prompt for the WebLogic Server username and password if the BDD_WLS_USERNAME and BDD_WLS_PASSWORD environment variables aren't set.

-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 stops all supported components gracefully.

Stopping Data Processing

Running stop on the dp and wm components has different effects on Data Processing:
  • Running it on the dp component disables the Hive Table Detector cron job, if it's currently enabled. This prevents the Detector from launching new Data Processing jobs, but doesn't affect current jobs or prevent new ones from being run by the Workflow Manager Service.
  • Running it on the wm component stops the Workflow Manager Service and cancels all currently-running Data Processing jobs. 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 before stopping the Workflow Manager Service, which may take a long time.

Be aware that no Data Processing jobs can run while the Workflow Manager Service is stopped. If you stop it but not the Hive Table Detector, the Detector will continue to run but will be ineffective since it submits all jobs to the Workflow Manager Service.

Examples

The following command gracefully shuts down all supported components: 
./bdd-admin.sh stop
The following command waits 10 minutes for the Dgraph HDFS Agent, Dgraph, and Workflow Manager Service to shut down gracefully, then terminates any that are still running: 
./bdd-admin.sh stop -t 10 -c agent,dgraph,wm