Difference between revisions of "Yerba"
From CoGepedia
(→Usage) |
|||
| Line 10: | Line 10: | ||
Yerba has two components the job daemon ''yerbad'' and the command line client ''yerba''. The job daemon is started started when the server is first booted Additionally, the work_queue catalog and worker pool need to be started as well. The command line client is used to check the status of the job engine. | Yerba has two components the job daemon ''yerbad'' and the command line client ''yerba''. The job daemon is started started when the server is first booted Additionally, the work_queue catalog and worker pool need to be started as well. The command line client is used to check the status of the job engine. | ||
| − | |||
| − | |||
==== yerbad<br> ==== | ==== yerbad<br> ==== | ||
Revision as of 11:13, 6 October 2013
Contents
Summary
Yerba is the job execution engine used by CoGe. For more details on how the job engine is used by CoGe refer to Job Execution Framework.
Installation
For installation instructions please refer to the github repository
Usage
Yerba has two components the job daemon yerbad and the command line client yerba. The job daemon is started started when the server is first booted Additionally, the work_queue catalog and worker pool need to be started as well. The command line client is used to check the status of the job engine.
yerbad
To start the job engine you need to start each script.
sudo /etc/init.d/catalog_server start sudo /etc/init.d/work_queue_pool start sudo /etc/init.d/yerba start
yerba
This command currently only checks for a response from the job engine.
$YERBA_DIR/bin/yerba
