Table of contents
- Introduction
- How to set priority for Data Engines
Introduction
The first article gave a general picture of what Data Engines and Queues are in Alumio. And as you may know, this functionality depends on priority.
If we know that Data Engines can perform actions to run processes in parallel, then they need to know which job to pick up first! That’s why setting a priority is so essential.
Navigate the path: Integrations > Configuration (Incoming, for example) > Scheduled Jobs to follow the topic.
How to set priority for Data Engines
In this question, our helper is Scheduler, where this functionality is placed. It doesn’t matter if you decide to add a new Scheduler from scratch via Settings > Schedulers or configuration, or edit an existing scheduler, priority will display at the bottom of the Scheduler details page.
Priority includes three available options:
- High;
- Medium;
- Low.
That means if you select three different options on three configurations, Data Engines will pick up the most priority process if processes run at the same time and no one has been selected before. If you run a process with a “medium” priority and have added one more scheduler with a “high” priority, Data Engines will pick up this configuration after finishing the current one.
Parallel processing helps Data Engines distribute the load on running configurations and finish processes faster without a long wait. However, pay attention, if your scheduler is disabled, Data Engines won’t pick up that configuration.