[ 
https://issues.apache.org/jira/browse/NIFI-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249100#comment-17249100
 ] 

ASF subversion and git services commented on NIFI-7856:
-------------------------------------------------------

Commit a73cd6a610f2e4a43e82bb26e2e4f983b9bfa1a5 in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a73cd6a ]

NIFI-7856: If a Provenance Event File is ready to be rolled over due to the 
maximum amount of time having elapsed, avoid rolling over unless there is at 
least one event written to the event file. Otherwise, we can have multiple 
RecordWriters / RecordWriterLeases pointing to the same file. This can result 
in data being overwritten, as well as failing to compress the event file upon 
rollover. Also added significant DEBUG/TRACE level logging.

Signed-off-by: Matthew Burgess <mattyb...@apache.org>

This closes #4580


> Provenance failed to be compressed after nifi upgrade to 1.12
> -------------------------------------------------------------
>
>                 Key: NIFI-7856
>                 URL: https://issues.apache.org/jira/browse/NIFI-7856
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.12.0
>            Reporter: Mengze Li
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.13.0
>
>         Attachments: 1683472.prov, NIFI-7856.xml, ls.png, screenshot-1.png, 
> screenshot-2.png, screenshot-3.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We upgraded our nifi cluster from 1.11.3 to 1.12.0.
> The nodes come up and everything looks to be functional. I can see 1.12.0 is 
> running.
> Later on, we discovered that the data provenance is missing. From checking 
> our logs, we see tons of errors compressing the logs.
> {code}
> 2020-09-28 03:38:35,205 ERROR [Compress Provenance Logs-1-thread-1] 
> o.a.n.p.s.EventFileCompressor Failed to compress 
> ./provenance_repository/2752821.prov on rollover
> {code}
> This didn't happen in 1.11.3. 
> Is this a known issue? We are considering reverting back if there is no 
> solution for this since we can't go prod with no/broken data provenance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to