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

facts GC can exceed jdbc max message size if too many paths are deleted

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PDB 2.3.8
    • Fix Version/s: PDB 2.3.8, PDB 3.2.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      3
    • Sprint:
      PuppetDB 2015-10-07

      Description

      This was reported on the puppet-users list here:
      https://groups.google.com/forum/#!topic/puppet-users/o_4K-UcuTQQ

      I don't know the specific context in which the user is encountering it, but I'm able to reproduce this issue by creating and storing a very large array-valued structured fact with map-valued elements, then updating the fact by inserting an element at the front of the array to force recomputation of all the paths. This problem was encountered on 2.3.7, but it affects master/3.x as well.

      We'll need to coordinate with the user to figure out what's going on with his particular setup. If this relates to a large array-valued structured fact, reformulating the top-level structure as a map would likely fix the issue. Ultimately, if we want to support arbitrarily large structured facts we'll want to expose jdbc's max message size as a tunable. Alternatively we should document our limits.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                wyatt Wyatt Alt
                QA Contact:
                Kurt Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: