[
https://issues.apache.org/jira/browse/NIFI-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-10051:
----------------------------
Fix Version/s: 1.16.3
> When a Controller Service is removed, its state should be cleared in a
> background thread
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-10051
> URL: https://issues.apache.org/jira/browse/NIFI-10051
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.17.0, 1.16.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, when a Processor is removed from the canvas, 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 already was done in NIFI-1606 for Processors but it never got done for
> Controller Services. We should do this for controller services as well.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
