[NIFI-5944] When NiFi restarts, if a component is expected to be running but is invalid, it never starts, even if becoming valid later

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 09/Jan/19 22:03
• Updated: 11/Jan/19 15:23
• Resolved: 11/Jan/19 15:23

Description

When NiFi starts up, if a component is expected to be running, NiFi will attempt to start the component. However, if the component is invalid for any reason, instead of starting the component, it throws an Exception and gives up. Instead, it should wait until the component becomes valid and then begin scheduling (or enabling, in the case of a controller service) the component.

Issue Links

• links to: GitHub Pull Request #3259
• links to: GitHub Pull Request #3263