Agree functionally How does this handle disk usage? Any manual intervention needed? What if the disk is full where it writes? What if the db somehow becomes corrupted?
Id like to ensure this thing is zero ops as much as possible such that in error conditions it resets and gets going again. Thanks On Wed, Jul 19, 2023 at 8:55 AM Pierre Villard <pierre.villard...@gmail.com> wrote: > I do think this provides great value. The possibility to get access to > status history of the components and at system level across restart is a > great improvement for NiFi troubleshooting. It also gives the ability to > store this information for a longer period of time. I'm definitely in favor > of making this the default starting with NiFi 2.0. > > Le mer. 19 juil. 2023 à 13:49, Simon Bence <simonbence....@gmail.com> a > écrit : > > > Hi Community, > > > > I was thinking if it would make sense to set the QuestDB as default for > > status history backend in 2.0? It is there for a while and I would > consider > > it as a step forward so the new major version might be a good time for > the > > wider audience. It comes with less memory usage for bigger flows, the > > possibility of checking status information when the node is not running > or > > restarted so I think it worth consideration. Any insight or improvement > > point is appreciated, thanks! > > > > Regards, > > Bence >
