[
https://issues.apache.org/jira/browse/NIFI-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Bence updated NIFI-8113:
------------------------------
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
was:
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:
* Hide current implementation behind an interface, making it interchangeable
between the existing and upcoming solutions
* Use QuestDB as backend
* Provide some rollback policy in order to avoid ever-growing database
> 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
> Fix For: 1.13.0
>
>
> 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)
