Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-8113

Persisting status history

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.14.0
    • Core Framework
    • None

    Description

      An alternative solution would be useful to replace/extend current in-memory solution for storing component and node metrics. This is in order to ease heap usage of NiFi which in case of high amount of processors (10-20k) might be significant and also to keep system information after shutting down.

      The solution should keep the data even if NiFi is stopped running and make it possible to read it out. It should be optimised for writing data as reading is much less frequent.

       

      Proposal:

      • Use QuestDB as backend
      • Add a new implementation for ComponentStatusRepository
      • Making it interchangeable between the existing and upcoming solutions
      • Provide some rollback policy in order to avoid ever-growing database

      Attachments

        Issue Links

          Activity

            People

              simonbence Simon Bence
              simonbence Simon Bence
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h 20m
                  4h 20m