[
https://issues.apache.org/jira/browse/NIFI-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704972#comment-14704972
]
Brian Ghigiarelli commented on NIFI-744:
----------------------------------------
We were running this patch for a week or so when it branched from 'develop.'
All seemed well and it "just worked," but we didn't attempt to stress the
system too much in that period (especially in regards to the edge cases you
mention in the below comment), nor did we closely monitor our IOPs except to
note that they didn't get worse.
We need to merge with the latest from master now and re-integrate this branch
to finish out the testing though. Assuming there aren't too many conflicts,
we'll likely be up and running with the latest + this patch branch in the next
couple days.
> Allow FileSystemRepository to write to the same file for multiple
> (non-parallel) sessions
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-744
> URL: https://issues.apache.org/jira/browse/NIFI-744
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-744-Refactored-ContentClaim-into-ContentClaim-a.patch
>
>
> Currently, when a ProcessSession is committed, the Content Claim that was
> being written to is now "finished" and will never be written to again.
> When a flow has processors that generate many, many FlowFiles, each in their
> own session, this means that we have many, many files on disk on the Content
> Repository, as well. Generally, this hasn't been a problem to write to these
> files. However, when the files are to be archived or destroyed, this is very
> taxing and can cause erratic performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
