You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/03/08 18:23:40 UTC

[jira] [Created] (NIFI-1606) When a component is removed, its state should be cleared in a background thread

Mark Payne created NIFI-1606:
--------------------------------

             Summary: When a component is removed, its state should be cleared in a background thread
                 Key: NIFI-1606
                 URL: https://issues.apache.org/jira/browse/NIFI-1606
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
            Reporter: Mark Payne
            Assignee: Mark Payne
             Fix For: 0.6.0


Currently, when a Processor is removed from the graph, the State Manager's onComponentRemoved method is called. This is called in a synchronous/blocking manner. By default, the timeout to communicate with ZooKeeper is 30 seconds. There are cases when the request can time out (for instance, due to improper Kerberos configuration), and with a 30 second timeout, this often results in nodes getting kicked out of the cluster.

However, if the request fails, we simply log a warning and move on. As a result, this synchronous network call should be moved to a background thread to ensure that it does not interfere with the web request to remove the component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)