[
https://issues.apache.org/jira/browse/NIFI-14212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985279#comment-17985279
]
Shubhra commented on NIFI-14212:
--------------------------------
Hi,
I tested this scenario and did not see the issue on the NiFi UI of the main
instance. However, I do see the issue on the backend test node (code/test
environment), exactly as described in this ticket.
Could this be a real issue, or is it caused by differences in configuration or
runtime behavior between the test and main environments?
> Improper state for disabled processors
> --------------------------------------
>
> Key: NIFI-14212
> URL: https://issues.apache.org/jira/browse/NIFI-14212
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mark Bean
> Assignee: Shubhra
> Priority: Major
>
> An INVALID processor can go to a STARTING state. Once in this state, the
> processor cannot be DISABLED or STOPPED; it remains in STARTING until the
> reason for being invalid has been corrected. And, once the invalid condition
> is corrected, the processor immediately enters a RUNNING state.
> To reproduce create a 2-processor flow: GenerateFlowFile > UpdateAttribute.
> Include a connection between them but do not add a connection or terminate
> the 'success' relationship of UpdateAttribute. Use "Start" on the operate
> palette or right-click context menu.
> Now, stop all processors using the same method as starting. Attempts to start
> all processors again fails. A dialog appears indicating that UpdateAttribute
> "cannot be started because it is not stopped. Current state is STARTING."
> The UpdateAttribute processor cannot be disabled because it is not in a
> STOPPED state.
> Now, set the 'success' relationship to terminate. The processor immediately
> goes into a RUNNING state. From the user perspective, this is a state change
> from INVALID to RUNNING which should not be allowed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
