Skip to content

FAQ

Jump to bottom
Ankit Nanglia edited this page Nov 11, 2019 · 2 revisions

Frequently asked questions

Kronos fails to start on adding a third party/ custom extension

  • Start by checking the Kronos scheduler/ executor logs.
  • Make sure all the required jars for the extensions are available in the lib/ext directory of the distribution.
  • Check if the extension configuration is correct and configured properly.

Refer Setting up distributed Kronos for example.

Why is my task in the workflow failing?

  • Kronos is only responsible for scheduling tasks defined in a workflow in a proper order to the executor. Executor takes care of executing the task by submitting it to proper handler.
  • Check the status of the job by calling the status API of Kronos and look for statusMessage to get more details.

GET /kronos/workflows/${workflow_name}/jobs

HEADERS namespace=${namespace_name}

The response is a list of all the jobs scheduled/executed. Copy the unique id of the job from the above response and execute below command to get the complete status of the job along with the status of tasks executed by the job.

GET /kronos/workflows/${workflow_name}/jobs/${job_id}

HEADERS namespace=${namespace_name}

The status API should provide enough details to debug the reason of failure. In case it doesn't help check the executor logs for more details.

Task is stuck in SCHEDULED state

A task is in SCHEDULED state when a task is sent for execution by the scheduler and is waiting for response from the executor. If the task is stuck in SCHEDULED state for long, one of the possible reason could be the QUEUE configuration or all of the executors are down. Check the queue configuration for error on the scheduler and executor side. Look for errors if any in the queue, scheduler and executor logs.

Clone this wiki locally