Appliance Job Queuing Reasons

Job queuing main reasons and its delay times are described here.

Jobs may queue on appliances for two main reasons:

Insufficient Resources: When all nodes are occupied, new jobs must wait until running jobs are complete, and resources become available.

Node Activation Delay: If nodes on the appliance are not in a ready state, they need to be started. Nodes idle for 10-15 minutes are powered down to save on cloud expenses. Depending on the node type, the time it takes for nodes to start ranges from 2 to 18 minutes. For graphical nodes used during sessions, the startup time is approximately 2 minutes.

When a user initiates a session on an appliance, it requires a node in the UP state. Nodes idle for more than 10-15 minutes are powered down to reduce cloud costs. Therefore, there can be a 3–4-minute delay for a session to be available for use.

Waiting time for requesting a new remote desktop session follows these steps:

  • A user creates a session request.

  • Interactive jobs are queued for access.

  • Runs the interactive jobs.

  • If a free node in the UP state is available, the job starts immediately (within 1 minute).

  • If there is no free node in the UP state, the system checks for node availability.

  • If no nodes are available, the jobs remain in the queue until a node becomes available.

  • If a node is available, it is powered on, and the session starts after 3-4 minutes.