[
https://issues.apache.org/jira/browse/NIFI-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793842#comment-17793842
]
Joe Witt commented on NIFI-12236:
---------------------------------
I think it would help to better explain what the properties/tunables are.
Maybe that is made available elsewhere but i'm not sure what batch size means
for this and I am also curious whether the user can control how much data is
retained and what the default is for that.
A path forward that I think keeps things moving but doesn't create new risks
currently not well enough explored
1. Avoid making this the default. It can be opted into.
2. Avoid making nifi-api changes.
3. Move this into its own nar instead of the core framework nar. It can
certainly still be included as it is today.
Remaining concerns can be addressed later and based on needs and findings from
actual usage.
Thanks
> 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: 1h
> 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)
