You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2016/07/22 16:11:20 UTC
[jira] [Created] (NIFI-2364) Node shouldn't be disconnected from a
cluster when clear component state operation gets error related to
underlying data source
Koji Kawamura created NIFI-2364:
-----------------------------------
Summary: 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: Bug
Components: Core Framework
Affects Versions: 1.0.0
Reporter: Koji Kawamura
Assignee: Koji Kawamura
Fix For: 1.0.0
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
(v6.3.4#6332)