Queue Control

Consider that you want to run all workspaces in repository Samples on two specific FME Engines.

First, create a queue, named Samples_Queue, that will hold the jobs that are routed to the specified engines. Next, create a job routing rule that routes jobs from the Samples repository to Samples_Queue:

• Type: Repository,
• Repositories: Samples
• Queue: Samples_Queue

Finally, create an engine assignment rule that assigns engines to run jobs routed to Samples_Queue:

• Type: Name
• Engines: Select the two FME Engines that you want to assign to queue Samples_Queue.
• Queues: Samples_Queue

Consider that you want to offload your highest-processing jobs to FME Engines that are installed on a separate server, named "FMEFlow2". On the Workspaces page, inside individual repositories, you can see some useful performance statistics for workspaces that have run jobs to date, or since the statistics were updated. You decide to offload jobs to this server based on a combination of Average % CPU > 80 and Average CPU Time > 1 Hour.

First, you create a separate queue, named queue_FMEFlow2, that will hold the jobs that are routed to the engines on FMEFlow2.

Next, you create a job routing rule that specifies: 1) Your job routing criteria—in this case, %CPU > 80 % AND CPU Time > 1 Hour; and 2) Jobs that meet these criteria are assigned to queue_FMEFlow2. (Note that you can assign a job routing rule to only one queue. A queue, however, can be assigned to multiple job routing rules.)

Finally, you create an engine assignment rule that specifies which engines run jobs that are routed to queue_FMEFlow2. You can specify the engines by name. However, a better option is to specify the engines based on a common system property assigned to all the engines installed on server FMEFlow2. On the Engines tab, you can see that one of the system properties assigned to your FME Engines is the server name on which they are installed. In this case, some of your engines are assigned the property FMEFlow2. This way, if you add more engines to FMEFlow2, they can also run jobs in the queue without explicitly adding them to this rule. (Note that more than one queue can be assigned to an engine assignment rule.)

1. Queues Tab: Create a Queue

1. On the Queues tab, click Create.
2. Enter a Name and Description (optional) for the queue.
3. Assign a Priority. The highest priority is 10 and the lowest priority is 1. Queues with higher priority submit job requests before queues with lower priority, depending on timing.
4. Click OK.

2. Job Routing Rules Tab: Assign the Queue to a Rule

To assign a queue to an existing rule:

1. Open the Job Routing Rules tab and click on a rule to open it.
2. In the Queue field, update the queue to which this rule applies.
3. Click OK.

To assign a queue to a new rule:

1. Open the Job Routing Rules tab and click Create.
2. On the Create Job Routing Rule page, specify the following:
   • A Name for the rule.
   • Type:
     • Properties: The queue handles jobs that meet the requirements of specified job performance measures or other properties, including one or more of the following:
       Expand for properties

       • % CPU: Jobs whose Average % CPU meets the requirements specified in the rule.
       • CPU Time: Jobs whose Average CPU Time meets the requirements specified in the rule.
       • Elapsed Time: Jobs whose Average Elapsed Time meets the requirements specified in the rule.
       • Peak Memory Usage: Jobs whose Average Peak Memory Usage meets the requirements specified in the rule.
       • Repository: Jobs that originate from workspaces in one or more specified Repositories.
       • Workspace: Jobs from one or more specified workspaces. Specify the repository, then the workspace.
       • Source Type: Jobs that originate from one or more specified FME Flow mechanisms.
       • Source Name: Jobs that originate from one or more named FME Flow items, such as the name of a schedule.
       • User Name: Jobs that run under the specified Username. For more information about the Username property, see Jobs (Completed, Queued, or Running).
       • User Role: Jobs that run under any Username belonging to one or more specified Roles. For more information about the Username property, see Jobs (Completed, Queued, or Running).

       Using boolean logic, specify the parameters of the Rule. To add parameters to the rule, click + Rule. To nest parameters in the rule, click + Ruleset.

       For example, to combine Average % CPU > 80 and Average CPU Time > 1 hour, specify % CPU > 80 % AND CPU Time > 1 Hour.

     Note   For a metric-based job routing rule to take effect, the workspace must have run enough times since statistics are initially collected or reset to generate a statistically significant sample. The required minimum number of jobs to run for a significant sample may vary between 30 to 100, depending on variability of data and the degree of precision required by the rule (for example, minutes versus seconds). The more variable the input data, and the higher degree of precision that is required of this data, the larger the sample size that is required. If a job routing rule does not reference a statistically significant sample of jobs run, the next applicable rule takes effect, by priority, or the job routes to the Default queue.
     • Repository: The queue handles jobs that originate from workspaces in one or more specified Repositories.
     Note  To combine repository with other criteria, specify Type: Properties, Rule: Repository, specify a repository, then add additional Properties.
   • Queue: Apply this rule to a queue.
   • Enabled: By default, the rule is enabled, which means that subsequent jobs that meet the requirements of the rule are routed to the specified Queue. If disabled, jobs that would otherwise route to this queue based on this rule instead route to the next applicable rule, by priority (see Prioritizing Job Routing Rules, below). If no other rules apply, jobs route to the Default queue.
3. Click OK.

3. Engine Assignment Rules Tab: Specify How Engines are Assigned to Queues

A set of engine assignment rules determines how engines are assigned to queues. You can assign queues to specific engines by name, or based on the properties of engines and queues.

To add a queue to an existing engine assignment rule:

1. Open the Engine Assignment Rules tab.
2. Click the rule to which you want to add the queue.
3. On the Editing Engine Assignment Rule page, add the queue to the Queues field.
4. Click OK.

To add a queue to a new rule

1. Open the Engine Assignment Rules tab, and click Create.
2. On the Create Engine Assignment Rule page, specify:
   • A Name for the rule.
   • Type:
     • Property: Engines are assigned to queues based on properties of engines and queues.
       • Rule: Using boolean logic, specify the properties that determine how engines are assigned to the specified queue(s).

       You can specify one or more of the following properties:

       Expand for properties
       • Dynamic: FME Engines license type is Dynamic.
       • Standard: FME Engines license type is Standard.
       • Custom: In addition to Dynamic and Standard, you can specify other engine properties as they appear on the Engines tab, such as the name or operating system of the host machine.
       • Physical Memory of Engine Host: Amount of RAM on the machine hosting an FME Engine.
       • Processor Count of Engine Host: Calculated as: (number of CPUs) x (number of Cores) x (number of hyperthreads) on the machine hosting an FME Engine.
       • Number of queued jobs: The number of jobs that are currently in a specified queue.
       • Longest queued job wait time: The time of the job that has been waiting the longest in a specified queue.
       • Time for all queued jobs to finish: The time for all jobs in a specified queue to finish based on historical data.
       • CPU for all queued jobs to finish: The CPU time for all jobs in a specified queue to finish based on historical data.
       • Number of Engines: The number of engines assigned to a specified queue. If you are concerned about the engine load of a particular queue based on current performance metrics of the queue's job routing rules, use this property to offload jobs to the queues you specify below, under Queues. For example, if queue MyQueue1 already has 5 engines assigned to it based on current performance metrics, use this property to offload jobs to other engines.

       The Rule drop-down is prepopulated with some properties from which to select. To add more properties to the drop-down, click Create Property. Beside Type, specify a property category, either Custom, Engine, or Queue. If Custom is specified, enter a Property exactly as it appears on the Engines tab. If Queue is specified, select a queue Property, and specify a queue to which the property should apply. If Engine is specified, select an engine host Property.

       Note  For Kubernetes deployments of FME Engines, specify Custom and the name property of the applicable engine deployment. For more information, see Defining FME Engines, Queue Control, and Streams to a Kubernetes Deployment.

       The rule appears beneath the Rule drop-down as you select properties. To add rules, click + Rule. To nest properties in the rule, click + Ruleset.

       For example, to specify any dynamic engine on server WHISTLER (a Custom property), specify Dynamic AND WHISTLER.

     • Name: Engines are assigned to queues by engine name.
       Note  For containerized deployments of FME Flow, such as Kubernetes, we strongly recommend specifying the engine name through the Property setting instead (see above).
       • Engines: Specify the engine names you want to assign to the queue(s).
       Note  You cannot specify any engines that are assigned to Streams.
   • Queues: Specify one or more queues to route jobs to engines specified in this rule.
   • Enabled: By default, the rule is enabled. If disabled, jobs that would otherwise route to engines based on this rule instead route to the Default queue.
   • Active Periods: Specify the Active Periods during which the engine assignment rule applies. If None, the rule always applies.
3. Click OK.