[NIFI-1183] Failed to stop failing processor

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.3.0
• Fix Version/s: 0.5.0
• Component/s: Core Framework
• Assignee: Oleg Zhurakousky
• Reporter: Oleg Zhurakousky
• Created: 17/Nov/15 19:17
• Updated: 16/Dec/15 20:38
• Resolved: 16/Dec/15 20:38

Description

The issue manifested itself with some failure in GetKafka. The thread dump appears to be pointing to deadlock originated with some Zookeeper failure

The general background to this is that in various cases there is a very key lock involved in ensuring the consistency of the nifi configuration. This is evident in the pathological case of a processor which for example has an OnScheduled method that never finishes. If the the user starts such a processor it will never actually start and further if they then try to stop that processor it will block indefinitely. The framework has to handle such cases in a deterministic manner and without resorting to blocking because no single bad processor should be able to bring down the house in such a case. This is not only present in this suggested path. It would apply to others so this needs holistic review and approach. Again, whenever this occurs it is a buggy and broken processor. But the framework must be able to handle these chaos monkey type processors in a deterministic manner.

Issue Links

• relates to: NIFI-1061 DBConnectionPool service unable to terminate
• relates to: NIFI-1164 Fix Race condition during initialization of ControllerServices