markap14 commented on PR #11204: URL: https://github.com/apache/nifi/pull/11204#issuecomment-4374573357
Hey @markobean I don't think this is the change we want to make. When you do a Bulk Start (e.g., at a Process Group level) it does intentionally start invalid processors. Without that, we had cases where you'd start a Process Group and think everything was running. But something was invalid so it didn't start. But then when you look a bit later, it's valid and just shows as STOPPED, leading users to think it just intermittently doesn't start components... and there are a lot of flows where processors are expected to become valid due to environment changes like a file becoming available. The concern in the Jira indicates "Once in this state, the processor cannot be DISABLED or STOPPED." That, I do not believe, is accurate, at a framework level. This sounds like a UI bug to me, where the UI doesn't allow you to click Stop. But if you were to stop the whole Process Group, it does stop the processor appropriately. I think I'd push more for a fix to the UI so that it allows stopping an invalid component. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
