[
https://issues.apache.org/jira/browse/NIFI-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuanhao Zhu updated NIFI-14548:
-------------------------------
Description:
We noticed that when a processor is referring to an invalid controller service,
now in nifi 2.x, if we want to start everything within the UI using context
menu e.g.
!image-2025-05-08-11-04-15-240.png!
!image-2025-05-08-11-04-33-787.png!
Then the invalid processor will start to flicker between invalid state and
stopped state, in this case, we cannot even disable the processor itself
anymore. Sometimes when the referred controller service suddenly becomes
invalid e.g. the file no longer exists, then the same flickering issue would
also happen and we get a error message from the toast "processor xxx cannot be
started because it is not stopped. Current state is STARTING"
Would you mind take a look at it? Thanks!
was:
We noticed that when a processor is referring to an invalid controller service,
now in nifi 2.x, if we want to start everything within the UI using context
menu e.g.
!image-2025-05-08-10-54-05-252.png!
Then the invalid processor will start to flicker between invalid state and
stopped state, in this case, we cannot even disable the processor itself
anymore. Sometimes when the referred controller service suddenly becomes
invalid e.g. the file no longer exists, then the same flickering issue would
also happen and we get a error message from the toast "processor xxx cannot be
started because it is not stopped. Current state is STARTING"
Would you mind take a look at it? Thanks!
> Processor referring to an invalid controller service flicker between stop and
> invalid state when attempting to start everything in the UI
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-14548
> URL: https://issues.apache.org/jira/browse/NIFI-14548
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Yuanhao Zhu
> Priority: Major
> Attachments: image-2025-05-08-10-54-05-252.png,
> image-2025-05-08-11-04-15-240.png, image-2025-05-08-11-04-33-787.png
>
>
> We noticed that when a processor is referring to an invalid controller
> service, now in nifi 2.x, if we want to start everything within the UI using
> context menu e.g.
> !image-2025-05-08-11-04-15-240.png!
> !image-2025-05-08-11-04-33-787.png!
> Then the invalid processor will start to flicker between invalid state and
> stopped state, in this case, we cannot even disable the processor itself
> anymore. Sometimes when the referred controller service suddenly becomes
> invalid e.g. the file no longer exists, then the same flickering issue would
> also happen and we get a error message from the toast "processor xxx cannot
> be started because it is not stopped. Current state is STARTING"
>
> Would you mind take a look at it? Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)