You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/15 17:01:00 UTC
[jira] [Commented] (NIFI-6033) ContentNotFoundException being
thrown when upgrading to 1.9.0-RC1
[ https://issues.apache.org/jira/browse/NIFI-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769503#comment-16769503 ]
ASF subversion and git services commented on NIFI-6033:
-------------------------------------------------------
Commit b508d6bfbc2b6a68fe2ab152de96611f06a8724a in nifi's branch refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b508d6b ]
NIFI-6033, NIFI-6034, NIFI-6035, NIFI-6036, NIFI-6037: Fixed bugs that were found during 1.9.0-RC1 validation. If multiple FlowFiles were written to same Content Claim, and a Processor attempted to read two of them wi within a single session, it would seek to the wrong part of the content or else throw a ContentNotFoundException. Updated logic for considering a processor to be 'running' / having 'active threads' if the processor is invalid upon NiFi restart but scheduled to run. Fixed NPE in FreeFormTextWriter. If MergeRecord reaches minimum number of records, flush writer after writing content out so that its minimum size can accurately be checked.
This closes #3309.
Signed-off-by: Bryan Bende <bb...@apache.org>
> ContentNotFoundException being thrown when upgrading to 1.9.0-RC1
> -----------------------------------------------------------------
>
> Key: NIFI-6033
> URL: https://issues.apache.org/jira/browse/NIFI-6033
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.9.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)