[NIFI-6033] ContentNotFoundException being thrown when upgrading to 1.9.0-RC1

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 14/Feb/19 18:45
• Updated: 15/Feb/19 17:00
• Resolved: 15/Feb/19 17:00

Description

I updated some servers that are used for always-on longer-term integration tests of NiFi to go from 1.8.0 to 1.9.0-RC1. After restart, I started seeing a lot of ContentNotFoundException's getting throwing:

2019-02-14 15:18:47,700 ERROR [Timer-Driven Process Thread-20] o.a.nifi.processors.standard.MergeRecord MergeRecord[id=35358bde-0165-1000-0000-00005fb05a10] Failed to bin StandardFlowFileRecord[uuid=90e5aaa4-2aa6-481d-8ddf-190e7ff40d79,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1550155044848-31, container=sda, section=31], offset=10032557, length=3852],offset=2660,name=20180813-433997.csv,size=1192] due to org.apache.nifi.controller.repository.ContentNotFoundException: Could not find content for StandardContentClaim [resourceClaim=StandardResourceClaim[id=1550155044848-31, container=sda, section=31], offset=10032557, length=3852]: org.apache.nifi.controller.repository.ContentNotFoundException: Could not find content for StandardContentClaim [resourceClaim=StandardResourceClaim[id=1550155044848-31, container=sda, section=31], offset=10032557, length=3852]
org.apache.nifi.controller.repository.ContentNotFoundException: Could not find content for StandardContentClaim [resourceClaim=StandardResourceClaim[id=1550155044848-31, container=sda, section=31], offset=10032557, length=3852]
at org.apache.nifi.controller.repository.StandardProcessSession.getInputStream(StandardProcessSession.java:2208)
at org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2290)
at org.apache.nifi.processors.standard.MergeRecord.binFlowFile(MergeRecord.java:364)
at org.apache.nifi.processors.standard.MergeRecord.onTrigger(MergeRecord.java:328)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:205)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException: null
at org.apache.nifi.stream.io.StreamUtils.skip(StreamUtils.java:259)
at org.apache.nifi.controller.repository.StandardProcessSession.getInputStream(StandardProcessSession.java:2179)
... 13 common frames omitted

 

It seems to be easily reproducible by using a Load-Balanced Connection feeding a MergeRecord processor.

Issue Links

• links to: GitHub Pull Request #3309