[
https://issues.apache.org/jira/browse/NIFI-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371911#comment-16371911
]
ASF GitHub Bot commented on NIFI-4774:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2416
The proposed solution does address the issue that was raised in NIFI-4774,
but in doing so introduces a new issue of data loss. This is why I provided the
solution that I did in the PR, as I believe that it addresses both of these
issues.
Again, I do not have a problem with making this new solution one that the
user is able to opt out of, though. If you want to submit a PR that also
incorporates your proposed solution into the MinimalLockingWirteAheadLog that
is okay too and we can also review and incorporate that change as well.
> FlowFile Repository should write updates to the same FlowFile to the same
> partition
> -----------------------------------------------------------------------------------
>
> Key: NIFI-4774
> URL: https://issues.apache.org/jira/browse/NIFI-4774
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.6.0
>
>
> As-is, in the case of power loss or Operating System crash, we could have an
> update that is lost, and then an update for the same FlowFile that is not
> lost, because the updates for a given FlowFile can span partitions. If an
> update were written to Partition 1 and then to Partition 2 and Partition 2 is
> flushed to disk by the Operating System and then the Operating System crashes
> or power is lost before Partition 1 is flushed to disk, we could lose the
> update to Partition 1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
