You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Dániel Bakai (Jira)" <ji...@apache.org> on 2020/03/11 02:12:00 UTC
[jira] [Created] (MINIFICPP-1174) Figure out how to clean up state
storage, if at all
Dániel Bakai created MINIFICPP-1174:
---------------------------------------
Summary: Figure out how to clean up state storage, if at all
Key: MINIFICPP-1174
URL: https://issues.apache.org/jira/browse/MINIFICPP-1174
Project: Apache NiFi MiNiFi C++
Issue Type: Task
Reporter: Dániel Bakai
I am not sure when we want to clean up state storage at all. For example, if a new configuration is loaded, we might want to clean the state of components that no longer exist in the flow, but this would mean that a single misconfiguration would make us loose our state (and that we can't properly roll back to an older configuration, because we have lost the state of processors no longer referenced). For the time being I think it is perfectly fine not to do any state cleanup: we don't have many processors using state, we don't have many instances of those processors that do use state, and states are small strings. We can handle the at maximum few hundred states stored in our DB (and this is the most extreme example I can imagine). If it really becomes an issue for someone, they can just delete the state directory/file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)