Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-2454

max-command-size default value is too small

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PDB 4.0.0
    • Fix Version/s: PDB 4.0.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      PuppetDB 2016-03-09

      Description

      Using a normal Puppet codebase on a small VM, it is very easy for catalogs to exceed the default max-command-size for PuppetDB. The following logs are an example run in the standard TSE environment, trying to compile a catalog for the Puppet Enterprise master.

      terminal

      [root@master ~]# puppet agent -t
      Info: Using configured environment 'production'
      Info: Retrieving pluginfacts
      Info: Retrieving plugin
      Info: Loading facts
      Error: Could not retrieve catalog from remote server: Error 400 on SERVER: [413 ] Command rejected due to size exceeding max-command-size
      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run
      

      puppetdb.log

      2016-02-19 19:47:49,891 INFO  [p.p.command] [52a2a9c4-3b8d-4226-96e6-726d4169a301] [replace facts] master.inf.puppetlabs.demo
      2016-02-19 19:47:54,921 WARN  [p.p.http] The root endpoint is experimental
      2016-02-19 19:47:56,892 WARN  [p.p.http] The root endpoint is experimental
      2016-02-19 19:48:05,540 WARN  [p.p.middleware] content-length of command is 1434722 bytes and is larger than the maximum allowed command size of 1242946 bytes
      2016-02-19 19:48:06,048 INFO  [p.p.command] [a10a6119-755e-4282-848c-657b381d1a40] [store report] puppet v4.3.2 - master.inf.puppetlabs.demo
      

      This should not occur under normal circumstances. The code and environment under which this error was generated is not an outlier in terms of how large catalogs get.

      If a max-command-size is to exist, then regardless of how much memory PuppetDB is allocated there should be a minimum floor for the automatically configured max-command-size and it should be high enough that customers will not hit it except under extremely unusual circumstances.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  reid Reid Vandewiele
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: