Details

    • Type: Epic
    • Status: Closed
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: pcp-broker 1.0.0
    • Component/s: pcp-broker
    • Labels:
      None
    • Epic Name:
      PCP Broker Reliability
    • Template:
    • Epic Status:
      To Do

      Description

      Improve the reliability of PCP broker. Some specific areas of improvement are

      • HUP reliability: configuration should reload after HUP, avoid losing messages through a HUP, clients should reconnect after HUP; check for ActiveMQ race-condition on HUP found in PuppetDB
      • ActiveMQ: upgrade to latest ActiveMQ, deal with issues arising from DB journaling (hypothesis for PCP-394)
      • Investigate broker performance; this may lead to considering alternatives to ActiveMQ, such as a new library being developed for PuppetDB, consider options for congestion control
      • Avoid adding redundant hop entries to the debug chunk

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              michael.smith Michael Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support