Uploaded image for project: 'Puppet Communications Protocol'
  1. Puppet Communications Protocol
  2. PCP-855

PE Tasks not handling puppetserver max_queued_requests/max_retry_delay properly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: pcp-broker, pxp-agent
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      Acceptance, 

      When we run PE-task, it has to establish a connection with request queue number nodes and remaining nodes to sleep and retry after max_retry _delay duration. 

      Show
      Acceptance,  When we run PE-task, it has to establish a connection with request queue number nodes and remaining nodes to sleep and retry after max_retry _delay duration. 
    • Team:
      Bolt
    • Method Found:
      Customer Feedback
    • CS Priority:
      Reviewed
    • QA Risk Assessment:
      Needs Assessment

      Description

      Hi, 

      When attempting to run PE task on the bulk of systems, few are established a connection and remaining failed with HTTP 503 error. This issue due to enabling ``max_queued_requests`` on PE. 

      Scenario, 

      When we enable jruby_puppet_max_queued_requests and jruby_puppet_max_retry_delay on PE, it will support to allow connection and remaining to be in the queue for retry. This is working for PE agent. When we run PE-task, it is establishing a connection with a max_queue_request number of nodes and remaining failed immediately without waiting to retry. 

       

      Error: Failed to execute the task for the non blocking 'task run' request (transaction 139). Error: Downloading the task file init.rb failed after trying all the available master-uris. Most recent error message: https://<puppet master host>:8140/puppet/v3/file_content/tasks/service/init.rb?environment=production returned a response with HTTP status 503. Response body: The number of requests waiting for a JRuby instance has exceeded the limit allowed by the max-queued-requests setting.

       

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              karthikeyan.kanagaraj Karthikeyan Kanagaraj
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support