[
https://issues.apache.org/jira/browse/NIFI-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192458#comment-15192458
]
ASF subversion and git services commented on NIFI-1606:
-------------------------------------------------------
Commit 5a8b2cf7f1c8df13720a74dd7f755343208c030f in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5a8b2cf ]
NIFI-1606: Run the onComponentRemoved logic of state providers in a background
thread
Signed-off-by: joewitt <joew...@apache.org>
> 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
>
> Attachments: NIFI-1606.patch
>
>
> 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)
