You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "markobean (via GitHub)" <gi...@apache.org> on 2026/05/04 18:21:01 UTC
[PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
markobean opened a new pull request, #11204:
URL: https://github.com/apache/nifi/pull/11204
…etual starting state disallowing changes
<!-- Licensed to the Apache Software Foundation (ASF) under one or more -->
<!-- contributor license agreements. See the NOTICE file distributed with -->
<!-- this work for additional information regarding copyright ownership. -->
<!-- The ASF licenses this file to You under the Apache License, Version 2.0 -->
<!-- (the "License"); you may not use this file except in compliance with -->
<!-- the License. You may obtain a copy of the License at -->
<!-- http://www.apache.org/licenses/LICENSE-2.0 -->
<!-- Unless required by applicable law or agreed to in writing, software -->
<!-- distributed under the License is distributed on an "AS IS" BASIS, -->
<!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -->
<!-- See the License for the specific language governing permissions and -->
<!-- limitations under the License. -->
# Summary
See Jira issue for details on the symptoms and procedure to replicate. In short, an INVALID processor can be stuck in an STARTING state making it impossible to configure or even stop. This PR resolves the issue. It ensures a Processor is not in an INVALID state prior to attempts to start.
There was a logging issue noted while investigating as well. The DEBUG log message indicated a time interval of 5 sec between successive attempts to start the Processor. The actual value is 500ms.
[NIFI-14212](https://issues.apache.org/jira/browse/NIFI-14212)
# Tracking
Please complete the following tracking steps prior to pull request creation.
### Issue Tracking
- [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created
### Pull Request Tracking
- Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000`
- Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000`
- Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status
### Pull Request Formatting
- Pull Request based on current revision of the `main` branch
- Pull Request refers to a feature branch with one commit containing changes
# Verification
Please indicate the verification steps performed prior to pull request creation.
### Build
- [X] Build completed using `./mvnw clean install -P contrib-check`
- [X] JDK 21
- [ ] JDK 25
### Licensing
- [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html)
- [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files
### Documentation
- [ ] Documentation formatting appears as expected in rendered files
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "markobean (via GitHub)" <gi...@apache.org>.
markobean commented on PR #11204:
URL: https://github.com/apache/nifi/pull/11204#issuecomment-4374189117
> @markobean Please see the requirement above for submitting signed commits.
Commit signed now.
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "markobean (via GitHub)" <gi...@apache.org>.
markobean commented on PR #11204:
URL: https://github.com/apache/nifi/pull/11204#issuecomment-4379255286
> Was the issue confirmed in a recent version of NiFi? I believe we can now properly stop such processors since NiFi 2.7.0 via [NIFI-14999](https://issues.apache.org/jira/browse/NIFI-14999).
Yes, the same behavior exists in 2.9.0.
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "dan-s1 (via GitHub)" <gi...@apache.org>.
dan-s1 commented on PR #11204:
URL: https://github.com/apache/nifi/pull/11204#issuecomment-4374398630
Hmm commit is still showing as `Unverified`.
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "markap14 (via GitHub)" <gi...@apache.org>.
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "markobean (via GitHub)" <gi...@apache.org>.
markobean commented on PR #11204:
URL: https://github.com/apache/nifi/pull/11204#issuecomment-4379677082
Cannot reproduce original issue. Closing.
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "dan-s1 (via GitHub)" <gi...@apache.org>.
dan-s1 commented on PR #11204:
URL: https://github.com/apache/nifi/pull/11204#issuecomment-4373670437
@markobean Please see the requirement above for submitting signed commits.
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "markobean (via GitHub)" <gi...@apache.org>.
markobean closed pull request #11204: NIFI-14212 fixed issue where an invalid processor could get in a perp…
URL: https://github.com/apache/nifi/pull/11204
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-14212 fixed issue where an invalid processor could get in a perp… [nifi]
Posted by "pvillard31 (via GitHub)" <gi...@apache.org>.
pvillard31 commented on PR #11204:
URL: https://github.com/apache/nifi/pull/11204#issuecomment-4377815604
Was the issue confirmed in a recent version of NiFi? I believe we can now properly stop such processors since NiFi 2.7.0 via NIFI-14999.
--
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: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org