Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
1.3.0
-
None
-
None
Description
After a crash resulting in data loss in my NiFi 1.3.0 cluster, the cluster came back up, but I was getting lots of "flow file content not found". I detached the node that was giving that error, made some flow changes, and then deleted its flow.xml.gz and restarted so it would rejoin the cluster.
Upon startup, it now gets the following error and shuts back down:
Caused by: java.lang.IllegalArgumentException: No enum constant org.wali.UpdateType.CONTENTMISSING
at java.lang.Enum.valueOf(Enum.java:238)
at org.wali.UpdateType.valueOf(UpdateType.java:24)
at org.apache.nifi.controller.repository.SchemaRepositoryRecordSerde.deserializeRecord(SchemaRepositoryRecordSerde.java:126)
at org.apache.nifi.controller.repository.SchemaRepositoryRecordSerde.deserializeEdit(SchemaRepositoryRecordSerde.java:109)
at org.apache.nifi.controller.repository.SchemaRepositoryRecordSerde.deserializeEdit(SchemaRepositoryRecordSerde.java:46)
at org.wali.MinimalLockingWriteAheadLog$Partition.recoverNextTransaction(MinimalLockingWriteAheadLog.java:1096)
at org.wali.MinimalLockingWriteAheadLog.recoverFromEdits(MinimalLockingWriteAheadLog.java:459)
at org.wali.MinimalLockingWriteAheadLog.recoverRecords(MinimalLockingWriteAheadLog.java:301)
at org.apache.nifi.controller.repository.WriteAheadFlowFileRepository.loadFlowFiles(WriteAheadFlowFileRepository.java:381)
at org.apache.nifi.controller.FlowController.initializeFlow(FlowController.java:713)
at org.apache.nifi.controller.StandardFlowService.initializeController(StandardFlowService.java:955)
at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:927)
... 4 common frames omitted
Attachments
Issue Links
- is related to
-
NIFI-3315 Changing default content repo location and restarting NiFi results in IllegalArgumentException
-
- Resolved
-
- links to