Managing Unravel services or daemons
Start a Specific Unravel Service or Daemon
To start a specific Unravel service or daemon, use the following command:
./manager start <service_name>
For example: ./manager start spark_worker
The above command will start all Spark worker daemons configured in the setup. If there are multiple Spark worker daemons, all of them will be started. If you need to start a specific instance of a daemon, use the service name with the node and instance number.
For example: ./manager start spark_worker_1_1
Refer to the following help command output for more details.
[unravel@ip-172-31-61-171 unravel]$ ./manager start --help +------------------------------------------------------------------------------- | manager start +------------------------------------------------------------------------------- | Start unravel or a specific service. | start : to start unravel | start SERVICE : to start a service | | Arguments: | service_name : Optional, Service name or alias |
Restart a Specific Unravel Service or Daemon
To restart a specific Unravel service or daemon, use the following command:
./manager restart <service_name>
For example: ./manager restart spark_worker
The above command will restart all Spark worker daemons configured in the setup. If there are multiple Spark worker daemons, all of them will be restarted. If you need to restart a specific instance of a daemon, use the service name with the node and instance number.
For example: ./manager restart spark_worker_1_1
Refer to the help command output given below for more details.
[unravel@ip-172-31-61-171 unravel]$ ./manager restart --help +------------------------------------------------------------------------------- | manager restart +------------------------------------------------------------------------------- | Restart unravel | | | Arguments: | service_name : Optional, Optional service name, if blank will apply to unravel as a whole |
Stop a Specific Unravel Service or Daemon
To stop a specific Unravel service or daemon, use the following command:
./manager stop <service_name>
For example: ./manager stop spark_worker
The above command will stop all Spark worker daemons configured in the setup. If there are multiple Spark worker daemons, all of them will be stopped. If you need to stop a specific instance of a daemon, use the service name with the node and instance number.
For example: ./manager stop spark_worker_1_1
Refer to the following help command output for more details.
[unravel@ip-172-31-61-171 unravel]$ ./manager stop --help +------------------------------------------------------------------------------- | manager stop +------------------------------------------------------------------------------- | Stop unravel or a specific service. | stop : to stop unravel | stop SERVICE : to stop a service | | Arguments: | service_name : Optional, Service name or alias |
Advanced configuration for Unravel services or Daemons
Use the following command to view all the available daemons even if Unravel is stopped:
./manager service list
The above command will show if the daemons are currently enabled or disabled.
To enable a daemon, run the following command. This command will enable the daemon permanently.
./manager service enable
<service>
--permanentTo update the configuration, run the following command:
./manager config apply
To disable a daemon, run the following command. This command will disable the daemon permanently.
./manager service disable
<service>
--permanentTo update the configuration, run the following command:
./manager config apply
To check all the available service names, run the following command:
./manager report
Notice
The following suffixes are added to the end of daemons:
M indicates a node number (multi-node deployment).
N indicates an instance number: 1, 2, 3, or 4. Instance numbers are separate daemons, which you can enable.
List of Unravel services available for databricks platform monitoring:
appstore_beats
appstore_flask
appstore_tasks
auto_action
config_service
datastore
dbx_worker
elasticsearch
event_worker
event_worker
hitdoc_loader
insights_worker
kafka
key_value_store
log_receiver
log_rotate
metrics_analyzer
nginx
ngui
opensearch
opensearch_dashboards
opensearch_doc_loader
pgsql
spark_worker
table_worker
task_worker
tidydir
unravel_monitor unravel_sensorzookeeper
Max memory settings for Unravel services
You can set the maximum memory for any Unravel services. This can be done only after you install or upgrade to Unravel version 4.7.5.0 or later.
Do the following to set the maximum memory for an Unravel service:
Stop Unravel.
<Unravel installation directory>/unravel/manager stop
Check the current memory settings.
<Unravel installation directory>/unravel/manager config memory show
For example:
manager config memory show -- Running: config memory show Instance key | Memory —--------------|------------ event_worker_1 | 2G log_receiver_1 | 4G …etc… -- OK
Run the following command:
<service-key>
: is the name of the daemon running the service. Refer to Unravel Daemons for the daemon names.<instance-key>
: is the name of the service instance.<value>
: memory value in Megabytes (M) or Gigabytes (G).
Note
If you provide the
<service-key>,
then the memory is set for all the instances in that service.If you provide the
instance-key
, then the memory is set only for a specific service instance.
<Unravel installation directory>/unravel/manager config memory set
<service-key|instance-key>
<value>
For example:
To set the maximum memory of all the instances of spark_worker to 6000 megabytes, run the following command:
/opt/unavel/manager config memory set spark_worker 6000
-- Running: config memory set spark_worker 6000 Setting memory for spark_worker_1 to 6000M Setting memory for spark_worker_2 to 6000M Setting memory for spark_worker_3 to 6000M Setting memory for spark_worker_4 to 6000M -- OK
To set all the memory of a specific spark_worker instance, such as spark_worker_1 to 6000 megabytes, run the following command:
/opt/unavel/manager config memory set spark_worker_1 6000
-- Running: config memory set spark_worker_1 6000M Setting memory for spark_worker_1 to 6000M -- OK
Apply the changes and restart Unravel.
<Unravel installation directory>/unravel/manager config apply --restart