Giulia, not sure if this is helpful or not. We had similar issues with NiFi 1.9.x but it was because we upgraded 1.9.0 -> 1.9.1 -> 1.9.2. The culprit was ever running 1.9.1. We saw issues if the node ever ran 1.9.1 on any of our NiFi instances then the data providence was corrupted.
"Corrupted" = Providence Events didnt show in the UI, or there was a long delay before the events showed up, or... strange behaviors. In short what we did was: 1) We created a new 1.9.2 install, used the nifi-toolkit to copy the flow from the repository, and started it again. 2) Set the logback.xml rollingPolicy's totalSizeCap to 10G and 5G 3) Appended a .gz extention in the logback.xml APP_FILE, USER_FILE, BOOTSTRAP_FILE fileNamePattern settings Its been running months without issues. I also recommend putting the provenance_repository directory on its own disk partition. If the root partition fills its game over for the NiFi instance. (In reality we put the nifi/content_repository, nifi/conf, nifi/flowfile_repository, nifi/provenance_repository each on their own disk partitions) Erik Anderson Bloomberg On Thu, Aug 1, 2019, at 9:31 AM, Joe Witt wrote: > Giulia, > > When you're experiencing this condition can you capture a thread dump and > share the logs (bootstrap/app)? To create this you can run > <where-nifi-installed>/bin/nifi.sh dump threaddump-locked-prov.log > > Thanks > > On Thu, Aug 1, 2019 at 3:57 AM Giulia Scalaberni > <[email protected]> wrote: >> Hi,____ >> Both on my 1.9.2 and 1.9.0 standalone installations data provenance is >> working correctly for nearly a month scheduled once a day then on the server >> all the data provenance in all individual processors and in the general >> reporting stays empty, even when I send new data through all the processors >> manually. ____ >> When opening a data provenance menu I see a very short popup menu appearing, >> but it closes for me too fast to see what is going on.____ >> On disk I still have more than 100GB available.____ >> The problem goes away when I restart the Nifi instance, and pops up again >> after nearly a month.____ >> *__ __* >> *__ __* >> Does anyone has the same behavior? Have you find a solution?____ >> __ __ >> Thank you in advance.____ >> __ __ >> Have a nice day,____ >> Giulia____ >> ____
