Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.6.0
-
None
Description
If using the SequentialAccessWriteAheadLog, once a journal becomes poisoned, NiFi can't recover without a restart.
SequentialAccessWriteAheadLog uses a LengthDelimitedJournal which has a "poisoned" flag[1]. This is initially set "false", but is set true if an Exceptions or Throwable is encountered on a write operation[2]. Once poisoned, calls to update()[3] will result in a call to checkState()[4] which then throws an IOException stating, "Cannot update journal file... If the repository is able to checkpoint, then this problem will resolve itself..." SequentialAccessWriteAheadLog.checkpoint()[5] creates a new LengthDelimitedJournal which would hypothetically have a cleared "poisoned" flag . However, before creating that new Journal, it calls journal.fsync()[6], which calls checkState(), which throws the above IOException if poisoned == true. So, the FlowFileRepository enters a state where it cannot be written to, and cannot recover, until the instance is restarted.
Attachments
Issue Links
- links to
