[jira] [Updated] (NIFI-2364) Node shouldn't be disconnected from a cluster when clear component state operation gets error related to underlying data source
[ https://issues.apache.org/jira/browse/NIFI-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 (v6.3.4#6332)
[jira] [Updated] (NIFI-2364) Node shouldn't be disconnected from a cluster when clear component state operation gets error related to underlying data source
[ https://issues.apache.org/jira/browse/NIFI-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-2364: Fix Version/s: (was: 1.0.0) 1.1.0 Affects Version/s: (was: 1.0.0) Status: Open (was: Patch Available) This issue happened after applying NIFI-2363 and testing with a clustered NIFI. Without NIFI-2363, all nodes will respond with the same response, and this will not happen. So, this issue is more a sub task of NIFI-2363. Spoked with Joe Witt and Joe Percivall about release target. Since there is not enough time to go though review & test cycle to be in 1.0. Also, cancel the patch to break it down to smaller PRs only focusing individual JIRA issue. > 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 >Reporter: Koji Kawamura >Assignee: Koji Kawamura > Fix For: 1.1.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)
[jira] [Updated] (NIFI-2364) Node shouldn't be disconnected from a cluster when clear component state operation gets error related to underlying data source
[ https://issues.apache.org/jira/browse/NIFI-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-2364: Issue Type: Sub-task (was: Bug) Parent: NIFI-2363 > 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 > 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)
[jira] [Updated] (NIFI-2364) Node shouldn't be disconnected from a cluster when clear component state operation gets error related to underlying data source
[ https://issues.apache.org/jira/browse/NIFI-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-2364: Status: Patch Available (was: Open) Changes are included in: https://github.com/apache/nifi/pull/563 > 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)
