druid/docs/design/peons.md
Gian Merlino d007477742
Docusaurus build framework + ingestion doc refresh. (#8311)
* Docusaurus build framework + ingestion doc refresh.

* stick to npm instead of yarn

* fix typos

* restore some _bin

* Adjustments.

* detect and fix redirect anchors

* update anchor lint

* Web-console: remove specific column filters (#8343)

* add clear filter

* update tool kit

* remove usless check

* auto run

* add %

* Fix resource leak (#8337)

* Fix resource leak

* Patch comments

* Enable Spotbugs NP_NONNULL_RETURN_VIOLATION (#8234)

* Fixes from PR review.

* Fix more anchors.

* Preamble nix.

* Fix more anchors, headers

* clean up placeholder page

* add to website lint to travis config

* better broken link checking

* travis fix

* Fixed more broken links

* better redirects

* unfancy catch

* fix LGTM error

* link fixes

* fix md issues

* Addl fixes
2019-08-20 21:48:59 -07:00

1.7 KiB

id title
peons Peons

Configuration

For Apache Druid (incubating) Peon Configuration, see Peon Query Configuration and Additional Peon Configuration.

HTTP endpoints

For a list of API endpoints supported by the Peon, please see the Peon API reference.

Peons run a single task in a single JVM. MiddleManager is responsible for creating Peons for running tasks. Peons should rarely (if ever for testing purposes) be run on their own.

Running

The Peon should very rarely ever be run independent of the MiddleManager unless for development purposes.

org.apache.druid.cli.Main internal peon <task_file> <status_file>

The task file contains the task JSON object. The status file indicates where the task status will be output.