[NIFI-2364] Node shouldn't be disconnected from a cluster when clear component state operation gets error related to underlying data source

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: Core Framework
• Assignee: Koji Kawamura
• Reporter: Koji Kawamura
• Created: 22/Jul/16 16:10
• Updated: 13/Oct/16 13:07

Description

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.

Issue Links

• blocks: NIFI-2078 State management for processors whose states are managed externally
• is related to: NIFI-2363 CLUSTER scope state should be viewed/cleared from primary node