nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Gresock <jgres...@gmail.com>
Subject Re: NiFi 1.11.1: EOFException in FlowFileAccessInputStream
Date Sat, 15 Feb 2020 00:35:33 GMT
Interestingly, this did not resolve the issue.  After another pod restart,
I have the same error at a MergeContent processor.  I verified that these
settings are all true.

org.apache.nifi.processor.exception.FlowFileAccessException: Could not read
from
StandardFlowFileRecord[uuid=b38e063f-23a4-47f6-bfff-81ac45277c38,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1581683172340-190097,
container=default, section=657], offset=0,
length=608],offset=464,name=94952c949967692e3bd9bddda4ea3ba26274ca22-ED,size=40]

Underlying exception is:
Caused by: java.io.EOFException: null
        at org.apache.nifi.stream.io.StreamUtils.skip(StreamUtils.java:270)
        at
org.apache.nifi.controller.repository.io.ContentClaimInputStream.formDelegate(ContentClaimInputStream.java:155)
        at
org.apache.nifi.controller.repository.io.ContentClaimInputStream.getDelegate(ContentClaimInputStream.java:51)
        at
org.apache.nifi.controller.repository.io.ContentClaimInputStream.read(ContentClaimInputStream.java:89)
        at
org.apache.nifi.controller.repository.io.LimitedInputStream.read(LimitedInputStream.java:86)
        at
org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.read(DisableOnCloseInputStream.java:49)
        at
org.apache.nifi.stream.io.ByteCountingInputStream.read(ByteCountingInputStream.java:52)
        at java.io.FilterInputStream.read(FilterInputStream.java:133)
        at
org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:82)
        ... 22 common frames omitted

On Fri, Feb 14, 2020 at 2:14 PM Joe Gresock <jgresock@gmail.com> wrote:

> Good idea.  I've made the change, and will report back if I see any more
> issues.
>
> On Fri, Feb 14, 2020 at 2:04 PM Joe Witt <joe.witt@gmail.com> wrote:
>
>> No it should not.  But if you want to rule out underlying storage not
>> getting the writes actually written you can use
>>
>> nifi.flowfile.repository.always.sync=true
>> nifi.content.repository.always.sync=true
>> nifi.provenance.repository.always.sync=true
>>
>> That will impact performance as it means we force sync to disk rather than
>> taking advantage of write ahead.  But try that and see if that helps in
>> your configuration.
>>
>> Thanks
>
>

-- 
Be on your guard; stand firm in the faith; be courageous; be strong.  Do
everything in love.    -*1 Corinthians 16:13-14*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message