[
https://issues.apache.org/jira/browse/NIFI-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024325#comment-18024325
]
ASF subversion and git services commented on NIFI-14999:
--------------------------------------------------------
Commit 739fea61909320dc0383658aaf0d58204f39ba95 in nifi's branch
refs/heads/main from Matt Gilman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=739fea6190 ]
NIFI-14999: Adding support to stop a starting processor. (#10344)
* NIFI-14999: Adding support to stop a starting processor.
* NIFI-14999: Addressing review feedback.
> Enabling service and referencing components makes invalid processor stuck as
> running
> ------------------------------------------------------------------------------------
>
> Key: NIFI-14999
> URL: https://issues.apache.org/jira/browse/NIFI-14999
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.5.0, 2.6.0
> Reporter: Gabriel Orstadius-Bui
> Assignee: Matt Gilman
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Found this bug in version 2.5, and have confirmed that this bug is not
> reproducible in 2.4
> # Create any Record Reader Service (don't enable yet)
> # Create a PutRecord processor and set the created Record Reader (don't set
> Record Destination Service)
> # Go to the Record Reader and enable it, selecting scope "Service and
> referencing components"
> # PutRecord will still be invalid (since "Record Distination Service" and
> Upstream Connection are required), but it is now not possible to change
> configurations or delete it, Error: "Cannot modify configuration of
> PutRecord[id=70b8bce2-0199-1000-4805-b0329e43f239] while the Processor is
> running".
> # UI also does not offer option to stop processor, only to disable (which
> does nothing)
> In other words, it seems as if enabling a service with referencing
> processors, wrongly leads the invalid processor to get stuck in a running
> state which can't be fixed, rendering the processor (and service) unusable.
> The only solution to this bug I have identified is to stop the entire Process
> Group, which then will stop the Processor gone rogue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
