[
https://issues.apache.org/jira/browse/NIFI-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291229#comment-17291229
]
ASF subversion and git services commented on NIFI-8113:
-------------------------------------------------------
Commit 99fe548e6bacb1c9ecc4a4a043197ae49962c177 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=99fe548 ]
NIFI-8113: Minor updates to admin guide to clarify documentation of some new
properties
> Persisting status history
> -------------------------
>
> Key: NIFI-8113
> URL: https://issues.apache.org/jira/browse/NIFI-8113
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Time Spent: 4h
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
