[
https://issues.apache.org/jira/browse/NIFI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894432#comment-15894432
]
ASF subversion and git services commented on NIFI-3548:
-------------------------------------------------------
Commit 4ed64e7561986c70a396a9c1af59b0efcc075c6c in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4ed64e7 ]
NIFI-3548: Fixed bug that caused failed requests to not get removed from
'request map' and also results in that preventing the purging logic, which
would then unintentially throw exceptions. This closes #1555
> Cluster Replication - Issue following MAX_REQUEST failures
> ----------------------------------------------------------
>
> Key: NIFI-3548
> URL: https://issues.apache.org/jira/browse/NIFI-3548
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Priority: Critical
> Fix For: 1.2.0
>
>
> Once a set number of requests fail, the request replicator will be unable to
> replicate new requests. This happens because on failure, the response is not
> cleaned up. Once we've encountered MAX_REQUEST failures, all subsequent
> requests will attempt to purge the previous responses. This action is causing
> the previous failure to be re-thrown. We need to update the request
> replication to:
> - Clean up failed responses
> - Do not re-throw the previous failures when attempting to purge
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
