Joseph Witt updated NIFI-2364:
    Fix Version/s:     (was: 1.1.0)

> Node shouldn't be disconnected from a cluster when clear component state 
> operation gets error related to underlying data source
> -------------------------------------------------------------------------------------------------------------------------------
>                 Key: NIFI-2364
>                 URL: https://issues.apache.org/jira/browse/NIFI-2364
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
> NodeClusterCoordinator.afterRequest() disconnects a node if it couldn't 
> handle mutation requests such as POST, assuming that node is not functioning 
> properly.
> However, if the cause of issue is related to an external data source, such as 
> Zookeeper or Kafka, other node will have the same problem even if other node 
> is elected as a primary node. In such case, disconnecting node wouldn't be a 
> good recovery solution. Instead, the node should keep connected, and let 
> users retry the operation.

This message was sent by Atlassian JIRA

Reply via email to