nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James McMahon <>
Subject Re: How to recover from a full provenance repository?
Date Mon, 13 Mar 2017 21:01:24 GMT
Here is all the info Joe. I had to manually recreate this here. Tried to
avoid typos. Anything that looks bizarre or oddly misspelled is on me.

Certainly Joe. I need to do whatever is humanly possible to get this up and
rolling again. Here is what I can provide:

/mnt/provenance_repo 50G size, 47G used, 17M available, 100% capacity
under this is
du -h output:
8.5M ./database_repository
16K ./lost+found
4.0K ./provenance_repository/index-1489...124
92K ./provenance_repository/toc
47G ./provenance_repository/journals
47G ./provenance_repository
47G .

In my
#H2 Settings
itory hours GB
nifi.provenance.repository.rollover.time=30 secs
nifi.provenance.repository.rollover.size=100 MB
nifi.provenance.repository.index.shard.size=500 MB
in nifi-bootstrap.log, No space left on device
similar error reported in nifi-app.log, fails when trying to create

I think both are just symptoms of the true problem, which is to say too
much stuff in
journals under provenance_repository

On Mon, Mar 13, 2017 at 4:10 PM, Joe Witt <> wrote:

> Jim,
> Processors create provenance events which get written to the
> provenenance repo but that is the end of their relationship.  The
> provenance repository is then self managing.  Can you share your
> provenance configuration?
> Thanks
> Joe
> On Mon, Mar 13, 2017 at 1:05 PM, James McMahon <>
> 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

View raw message