Queue registration form for recommendation process

  • Release version: Yokohama
  • Updated May 15, 2025
  • 1 minute to read
  • The Recommended Actions use the queue registration form to create queues for recommendation process.

    Table 1. Queue Registration form
    Field Description
    Suffix Suffix of the queue. For example, ra_processor_queue_1.
    Note:

    When creating additional custom queues beyond the default ra_processor_queue_1, it's important to follow the established naming convention to ensure proper system recognition and functionality.

    You should increment the trailing number in the queue name accordingly. For the second queue, name it as ra_processor_queue_2 and so on. Continue this pattern for subsequent queues. Maintain the exact naming pattern to avoid configuration issues.

    Application Associated application name or identifier.
    Queue Title of the selected queue. For example, sn_nb_action.ra_processor_queue_1.
    Automatic Job Scheduling Option to enable the automated job schedule for the queue.
    Event Processing Order Sequence in which events are processed.
    Job Configuration type Definition of how jobs are configured or processed.
    Scale Factor Number of polling jobs created for a particular queue.
    Note:

    Each application node gets a job and an order according to queue. The customer can increase the value up to a maximum of 3. Increasing the scale factor creates more polling jobs according to application node for that queue.

    For configuring queues:
    • You can create a maximum up to 8 custom queues for a recommended action use case.
    • Only one queue with one scale factor and a 10-second poll interval is shipped out of the base system.
    For a higher load:
    • Increase number of queues.
    • Adjust scale factors accordingly.
    • Consider adding nodes, if needed.
    • Decrease polling interval.
    Poll Interval The poll interval is the waiting time before the queue is processed. It determines how often the queue is polled, that is, how frequently new events are fetched.
    Note:
    You can customize to a lower value (for example, 1 second) for reduced latency. The default poll interval is every 10 seconds.

    You can reduce the interval to 1 second to decrease waiting time.

    Decreasing the value to a lower number might cause acquiring most of the worker threads. Those threads are picked for RA use-case and can cause delays to other tasks on the instance.

    The poll interval displays the duration in:
    • Days: Shows the number of days the queue has been added.
    • Hours: Indicates the duration (in seconds, minutes, or hours) that an event has been in the queue once added.
    Description Additional details about the queue.