[
https://issues.apache.org/jira/browse/NIFI-14591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953487#comment-17953487
]
ASF subversion and git services commented on NIFI-14591:
--------------------------------------------------------
Commit bb234ba960d6bda6c2b11b1b702fbd3aad98a562 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=bb234ba960 ]
NIFI-14591 Fixed Stateless Process Group Enabling with Controller Services
(#9966)
When a stateless group is started, wait Controller Services to enable. If
Process Group is stopped in the meantime, disable the controller services.
If unable to transition Controller Service state to ENABLING when enable() is
called, use future.complete(null) instead of future.completeExceptionally(...).
While future.completeExceptionally is more correct in this situation, it does
change behavior unexpectedly and is not the real intent of this code change.
Signed-off-by: David Handermann <[email protected]>
> Stateless Process Group cannot be stopped if Controller Services fail to
> enable
> -------------------------------------------------------------------------------
>
> Key: NIFI-14591
> URL: https://issues.apache.org/jira/browse/NIFI-14591
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Create a Process Group and set the Execution Engine to Stateless. Configure a
> Controller Service in such a way that it is valid but will fail when enabling
> (e.g., an invalid hostname in a DBCP Connection Service). When you start the
> Stateless Process Group, the Controller Service will become ENABLING but will
> never stop trying to enable. Even if you stop the Process Group, it stays in
> that state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
