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

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

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

NIFI-7346: Ensure that the Provenance Repository doesn't delete the Active 
Event File


> Provenance Repository can stop producing data and become empty
> --------------------------------------------------------------
>
>                 Key: NIFI-7346
>                 URL: https://issues.apache.org/jira/browse/NIFI-7346
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.12.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The Provenance Repository is designed to periodically age off old data. This 
> is done by looking at the Last Modified Time for all event files, and then 
> removing any file whose Last Modified Time is longer than the configured 
> "nifi.provenance.repository.max.storage.time" time.
> However, it does this without first checking if the event file is the 
> "active" event file. As a result, it can delete the event file while it is 
> being written to. If this happens, on Linux and OSX, the delete will succeed 
> and any further writes to the underlying file handle will simply disappear. 
> And checking the size of the file will always return 0.
> As a result, the Event File will never roll over because it never reaches the 
> max size. And it doesn't roll over based on time due to NIFI-7339. As a 
> result, all data will be aged off from the Provenance Repository and no new 
> data will be added until restart.



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

Reply via email to