Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
In the process of testing NIFI-2160 and NIFI-2344, we found that if a controller service throws some type of RuntimeException(e.g. IllegalStateException) in its @OnEnabled method it will essentially "break the chain" of startup of things that depend on it. The end result is that in a cluster, you can have a processor that is running on some nodes and stopped on others. This probably isn't the desired behavior. In StandardControllerServiceProvider[1] when thrown Exceptions are caught, we should possibly retry enabling the service. If it can't be enabled... we might want to consider shutting down NiFi. That's sort of extreme, but allowing the cluster to enter an inconsistent state seems like a bad thing. We could possibly also come up with some way of indicating there's an inconsistency in the UI. The proper solution will require some consideration, but the issue needs to be addressed somehow.
Attachments
Issue Links
- is related to
-
NIFI-2492 Processor startup issue
- Resolved