1.1.0, it's not on a system I can copy/paste from, but here's part of the stack trace:
at org.wali.MinimalLockingWriteAheadLog$Partition.endRecovery(MinimalLockingWriteAheadLog.java:1047) ~[nifi-write-ahead-log-1.1.0.jar:1.1.0] at org.wali.MinimalLockingWriteAheadLog.recoverFromEdits(MinimalLockingWriteAheadLog.java:487) ~[nifi-write-ahead-log-1.1.0.jar:1.1.0] at org.wali.MinimalLockingWriteAheadLog.recoverRecords(MinimalLockingWriteAheadLog.java:301) ~[nifi-write-ahead-log-1.1.0.jar:1.1.0] On Wed, Sep 6, 2017 at 4:13 PM, Mark Payne <[email protected]> wrote: > Joe, > > What version of NiFI are you running? Do you have a stack trace? > > Thanks > -Mark > > > > On Sep 6, 2017, at 11:59 AM, Joe Gresock <[email protected]> wrote: > > > > I'm wondering if there is a way to recover from this scenario: > > > > ERROR [main] o.a.nifi.controller.StandardFlowService Failed to load flow > > from cluster due to: org.apache.nifi.cluster.ConnectionException: > Failed to > > connect node to cluster due to: java.lang.IllegalStateException: > Signaled > > end to recovery, but there are more recovery files for Partition in > > directory /data/nifi/flowfile_repository/partition-8 > > > > I have nearly a TB of files in my content_repository, so I'd really like > to > > be able to salvage this node, but I'm not sure how to proceed, as the > node > > won't start up. > > > > -- > > I know what it is to be in need, and I know what it is to have plenty. I > > have learned the secret of being content in any and every situation, > > whether well fed or hungry, whether living in plenty or in want. I can > do > > all this through him who gives me strength. *-Philippians 4:12-13* > > -- I know what it is to be in need, and I know what it is to have plenty. I have learned the secret of being content in any and every situation, whether well fed or hungry, whether living in plenty or in want. I can do all this through him who gives me strength. *-Philippians 4:12-13*
