[
https://issues.apache.org/jira/browse/NIFI-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553146#comment-15553146
]
ASF subversion and git services commented on NIFI-2836:
-------------------------------------------------------
Commit 09568d092b5329e4732f2e05c10fad181c344b8d in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=09568d0 ]
NIFI-2836:
- Ensure that we wait until a request is completed before unlocking the lock
for request replication
- Ensure that failures do not trigger request completion logic unless the
failure is the last node to report its status
- This closes #1109
> Cluster - Request Replication
> -----------------------------
>
> Key: NIFI-2836
> URL: https://issues.apache.org/jira/browse/NIFI-2836
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.1.0
>
>
> When a request is replicated throughout the cluster, the cluster coordinator
> needs to ensure that request completes (including both parts of the two-phase
> commit if applicable) prior to replicating the next request.
> Looks like a write lock is obtained while submitted a background task. The
> actually work completes outside the locks scope.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
