Ensure the Onboarder worker is always running¶
A systemd
daemon is used to manage the PIM Onboarder woker(s). It allows multiple operations such as:
- start/stop/restart a worker
- check the status of a worker
- enable or disable a worker
- see the logs of a worker
Please note that, while the number of running workers is not enforced, it is not recommended to increase it above the server capability. Between 1 and 3 workers is recommended. You should also take into account how many job queue consumer are running as they take resources too.
Create a new worker by enabling & starting a service with a unique identifier:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | # Enable the worker #1
partners_systemctl pim_onboarder_worker@1 enable
# Launch the worker #1
partners_systemctl pim_onboarder_worker@1 start
# Enable the worker #2
partners_systemctl pim_onboarder_worker@2 enable
# Launch the worker #2
partners_systemctl pim_onboarder_worker@2 start
# Check the status of the worker #1
partners_systemctl pim_onboarder_worker@1 status
# Stop the worker #2
partners_systemctl pim_onboarder_worker@2 stop
# Disable the worker #2
partners_systemctl pim_onboarder_worker@2 disable
|
Useful commands¶
1 2 | # check the status of all running workers
partners_systemctl pim_onboarder_worker@* status
|
Found a typo or a hole in the documentation and feel like contributing?
Join us on Github!