Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-377

Consider splitting metrics and state variables in ConsensusQueue

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: M4
    • Fix Version/s: None
    • Component/s: consensus
    • Labels:
      None

      Description

      Right now we're using metrics to store queue state, which we use to make behavioral decisions. Adar makes the point that metrics should be optional and resettable, in which case the current implementation would be plainly wrong. If we evet want Kudu to support such behavior we need to split the metrics into metrics and state variables.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              dralves David Alves
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: