[NIFI-10051] When a Controller Service is removed, its state should be cleared in a background thread

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.17.0, 1.16.3
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 24/May/22 21:02
• Updated: 13/Jun/22 15:36
• Resolved: 26/May/22 14:33

Description

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.

Issue Links

• links to: GitHub Pull Request #6078