The Peon service is a task execution engine spawned by the MiddleManager. Each Peon runs a separate JVM and is responsible for executing a single task. Peons always run on the same host as the MiddleManager that spawned them.
For basic tuning guidance for MiddleManager tasks, see Basic cluster tuning.
Peons run a single task in a single JVM. The MiddleManager is responsible for creating Peons for running tasks. Peons should rarely run on their own.
The Peon should seldom run separately from the MiddleManager, except 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.