Thank you very much James. I suspect that it may well come down to me doing as you suggest as my "drop back and punt" option. Joe is going to take a look at my situation to see if anything jumps out so that I don't get myself in the same situation once I migrate to production.
Jim On Mon, Mar 13, 2017 at 4:15 PM, James Wing <jvw...@gmail.com> wrote: > Jim, > > The good news is that you can delete the entire ./provenance_repository > and NiFi will start up with a fresh clean one. Of course, that won't solve > your analysis challenge. > > You might want to play around with some of the provenance config entries > to limit the repository, like nifi.provenance.repository.max.storage.time > and nifi.provenance.repository.max.storage.size. That should help > prevent you from running out of space, even if it doesn't tell you exactly > where all the entries came from. > > > Thanks, > > James > > On Mon, Mar 13, 2017 at 1:05 PM, James McMahon <jsmcmah...@gmail.com> > wrote: > >> Good evening. I have a number of process groups in my NiFi instance that >> run concurrently. Evidently I have filled up my provenance repo. How do I >> recover from this? NiFi will not start back up after shutdown. >> >> I am in a dev environment right now so I can afford to lose what had been >> in my flows. Does that give me other options to recover? >> >> However I must determine what process group and processor are not freeing >> resources from the provenance repo. I can't allow this workflow to promote >> to production until I determine how to prevent this from reoccurring. How >> can I do that? >> >> My provenance, content, and flow repos are all on separate disk devices, >> each of which is 50GB in capacity. >> >> Thank you for your help. -Jim >> > >
