[
https://issues.apache.org/jira/browse/NIFI-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466371#comment-16466371
]
ASF subversion and git services commented on NIFI-5153:
-------------------------------------------------------
Commit 8acac9cba5b9d409e4ba885ce5dba15ef416de0e in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8acac9c ]
NIFI-5153: If a node is disconnected due to failure to complete mutable
request, the node should be allowed to rejoin
This closes #2677.
Signed-off-by: Bryan Bende <bbe...@apache.org>
> When a node fails to perform a mutable request, it should be asked to rejoin
> cluster instead of being disconnected
> ------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-5153
> URL: https://issues.apache.org/jira/browse/NIFI-5153
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.7.0
>
>
> Currently, if a mutable request (POST, PUT, DELETED) is issued to a cluster,
> the request is replicated and if any node fails to perform the request, it is
> disconnected (unless all nodes fail, in which case no node is disconnected).
> However, often times, the failure is due to some sort of socket timeout. As a
> result, we should request that the node re-join the cluster, as long as its
> flow matches the cluster's flow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
