You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/12/18 22:39:46 UTC

[jira] [Updated] (NIFI-1310) S2S data stops to all nodes when one node can not be reached

     [ https://issues.apache.org/jira/browse/NIFI-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt updated NIFI-1310:
------------------------------
    Fix Version/s: 0.4.1
                   0.5.0

> S2S data stops to all nodes when one node can not be reached
> ------------------------------------------------------------
>
>                 Key: NIFI-1310
>                 URL: https://issues.apache.org/jira/browse/NIFI-1310
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.4.0
>            Reporter: Matthew Clarke
>            Priority: Critical
>             Fix For: 0.5.0, 0.4.1
>
>
> let me setup the scenario  that causes S2S to fail.
> - I have a 3 Node cluster that is receiving data via S2S.
> - I bring down the NCM for that cluster.
> - Data continues to be delivered to nodes but sending NiFi can no longer update remote group peers because NCM is down.
> Everything is working as expected here.
> if one of those Nodes should then go down while the NCM is still not available, dataflow to remaining two nodes will stop as well within a few minutes.
> The expected behavior is that the sending NiFi with the RPG will fail on the one lost Node, but still continue sending data to the other two available nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)