I noticed, too, that I have many partitions, partition-0 to partition-255 to be exact. These all have journal files in them. So I suspect that the journal file I cited is not specifically the problem in and of itself, but instead is the point where the allowable open files threshold is reached. I'm wondering if I have to recover by deleting all these partitions? -Jim
On Tue, Mar 28, 2017 at 5:58 AM, James McMahon <[email protected]> wrote: > While trying to use Python logging from two scripts I call via two > independent ExecuteScript processors, I seem to have inadvertently created > a condition where I have too many files open. This is causing a serious > challenge for me, because when I attempt to start nifi (v0.7.1) it fails. > > The log indicates that the flow controller cannot be started, and it cites > the cause as this: > org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller > . > . (many stack trace entries) > . > Caused by: java.nio.file.FileSystemException: /mnt/flow_repo/flowfile_ > repository/partition-86/83856.journal: Too many files open > > In a situation like this, what is the best practice for recovery? Is it > permissible to simply delete this journal file? What are the negative > repercussions of doing that? > > I did already try deleting my provenance_repository, but that did not > allow nifi to restart. (NiFi did re-establish my provenance_repository at > restart). > > Thanks very much in advance for your help. -Jim >
