Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1695

Add ability to reject API submissions that would lead to memory exhaustion

          Details

          • Type: New Feature
          • Status: Resolved
          • Priority: Normal
          • Resolution: Done
          • Affects Version/s: None
          • Fix Version/s: None
          • Component/s: None
          • Labels:
          • Template:
          • Team:
            Systems Engineering
          • Story Points:
            3
          • Sprint:
            SE 2017-01-11, SE 2017-01-25, SE 2017-02-08
          • QA Risk Assessment:
            Needs Assessment

            Description

            Puppet agents can submit large datasets during API requests. When the Puppet Server buffers enough of these into memory, it can end up running out of resources. An option similar to PuppetDB's reject-large-commands setting would allow the Puppet Server to remain operational by refusing to accept large API submissions and also increases the visibility of problematic agents.

              Attachments

                Issue Links

                is supported by

                New Feature - A new feature of the product, which has yet to be developed. PDB-156 Handle large catalog sizes gracefully

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Closed
                relates to

                Improvement - An improvement or enhancement to an existing feature or task. TK-431 Add stream limit and consumption to request-body-max-size webserver setting

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Accepted

                  Activity

                    People

                    • Assignee:
                      jeremy.barlow Jeremy Barlow
                      Reporter:
                      chuck Charlie Sharpsteen
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Zendesk Support