Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-2363 CLUSTER scope state should be viewed/cleared from primary node
  3. NIFI-2364

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

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.0.0
    • None
    • Core Framework
    • None

    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.

      Attachments

        Issue Links

          Activity

            People

              ijokarumawak Koji Kawamura
              ijokarumawak Koji Kawamura
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: