Unravel Daemons
The Unravel service is composed of many daemons which are summarized in the following table. The suffix _N means 1, 2, 3, or 4 separate daemons which you can enable. Refer to Enabling multiple daemons for high-volume data.
Daemon Logical Name | Description |
|---|---|
| AutoAction worker |
| BigQuery worker |
| Datastore REST API HTTP server |
| Elasticsearch |
| Event worker |
| Health check |
| Hitdoc Loader |
| Hive worker |
| Hive Hook Worker EMR |
| Host Monitor |
| Impala worker |
| Bundled Kafka (on a custom port) |
| Kafka Monitor |
| Log Receiver |
| |
| Metrics Analyzer |
| MySQL |
| Angular Web UI |
| Oozie v3 sensor |
| Spark Worker |
| Table Worker |
| Task worker |
| Tidy Dir cleans up and archives hdfs directories, db retention cleaner. |
| Cluster Access Service - provides access to cluster services and files (Unravel Edge node). |
| Databricks sensor (Unravel remote node) |
| EMR sensor (Unravel remote node) |
| Job Analyzer summarizes jobs |
| Job Collector sensor YARN for EMR |
| Universal sensor |
| Job Collector sensor YARN |
| Job Collector sensor worker YARN |
| Bundled Zookeeper (on a custom port) |
When you start Unravel, all the daemons are started automatically. However, if you want to start a single Unravel daemon separately, run the following command:
<Unravel installation directory>/unravel/manager start <daemon>
##For example:
/opt/unravel/manager start unravel_sensor_1When you want to enable a specific daemon, run the following command:
<Unravel installation directory>/unravel/manager service enable <daemon>
##For example:
/opt/unravel/manager service enable unravel_sensor_1