[
https://issues.apache.org/jira/browse/NIFI-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18022697#comment-18022697
]
Gabriel Orstadius-Bui commented on NIFI-14999:
----------------------------------------------
Hi [~mcgilman], thanks for looking into this issue and opening a PR to address
it.
It would be great though if the Processor did not get set to STARTING at all
when requesting the Service's referencing components to start (since it is
invalid even after enabling the service).
I set breakpoints in the code and noticed that when calling the endpoint, each
component gets verified if it can start (done in verifyCanStart() in
StandardProcessorNode) - but only the Processor's current ScheduleState is
checked, not if the Processor has Validation Errors.
Then again, the processor wouldn't get started in version 2.4.0 and I couldn't
find any relevant changes in the code, so not sure why this bug has now
appeared.
> 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: 10m
> 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)
