[
https://issues.apache.org/jira/browse/NIFI-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794392#comment-17794392
]
David Handermann commented on NIFI-12236:
-----------------------------------------
To help move things forward, I created a separate Jira issue NIFI-12492 for
moving QuestDB to its own NAR and submitted a pull request for review.
I realize that moving the components around would require rebasing the changes,
but the goal is to address one of the concerns about continued maintenance of
the QuestDB implementation. With the StatusHistoryRepository as an existing
extension point, having a separate NAR makes it much easier to iterate and
improve the implementation without changes to the framework itself.
I was able to incorporate upgrading from QuestDB 7.2 to 7.3.7 for NIFI-12435,
as the differences were minimal.
The move to a separate NAR did not require any code changes, other than the
minor adjustments for updating to QuestDB 7.3.7.
Although not wanting to slow progress on the more fundamental improvements,
moving the implementation to a separate NAR should address some general
concerns and provide a better path forward.
> Improving fault tolerancy of the QuestDB backed metrics repository
> ------------------------------------------------------------------
>
> Key: NIFI-12236
> URL: https://issues.apache.org/jira/browse/NIFI-12236
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Based on the related discussion on the dev email list, the QuestDB handling
> of the metrics repository needs to be improved to have better fault tolerance
> in order to be possible to use as a viable option for default metrics data
> store. This should primarily focus on handling unexpeted database events like
> corrupted database or loss of space on the disk. Any issues should be handled
> with an attempt to keep the database service healthy but in case of that is
> impossible, the priority is to keep NiFi and the core services running, even
> with the price of metrics collection / presentation outage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
