mosermw opened a new pull request, #10309: URL: https://github.com/apache/nifi/pull/10309
# Summary [NIFI-14975](https://issues.apache.org/jira/browse/NIFI-14975) On startup, bad configuration or startup errors can cause NiFi Registry to successfully start and the web UI works, but Jetty can return 503 UNAVAILABLE errors on nifi-registry-api. One (of many) conditions this can happen is if the configuration is fine but an LdapUserGroupProvider or DatabaseUserGroupProvider cannot connect to external services. This PR causes NiFi Registry to shutdown in these conditions. This aligns with how NiFi behaves in similar scenarios. It also works well in containerized environments, where an orchestrator can now notice Registry is not healthy and retry startup. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] 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 ### Licensing - [n/a] 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) - [n/a] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [n/a] 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
