markap14 opened a new pull request, #11615: URL: https://github.com/apache/nifi/pull/11615
# Summary [NIFI-16284](https://issues.apache.org/jira/browse/NIFI-16284) `ClusteredConnectorBacklogIT#testClusteredReadQueueAttributesLoadBalancedConnection` fails intermittently in CI during teardown when deleting the Connector, because FlowFiles remain queued after the drop/purge. The sibling `DO_NOT_LOAD_BALANCE` test has not shown this, which points at Load Balancing as a factor. The working theory is that a drop request can complete while FlowFiles are in flight on a load-balanced queue, then those records land on a peer after purge. This PR does not change framework drop/purge behavior. It waits in the test until no connection reports `LOAD_BALANCE_ACTIVE`, after Connector creation, in a `finally` block so the wait still runs if start, stop, or assertions fail. This is a hypothesis-driven mitigation; the original race could not be reproduced on demand. # Tracking - [x] Apache NiFi Jira issue created - [x] Pull Request title starts with Apache NiFi Jira issue number - [x] Pull Request commit message starts with Apache NiFi Jira issue number - [x] Pull request contains commits signed with a registered key # Verification - Ran `ClusteredConnectorBacklogIT#testClusteredReadQueueAttributesLoadBalancedConnection` locally (`./mvnw -pl nifi-system-tests/nifi-system-test-suite -Pintegration-tests,skip-unit-tests verify -Dit.test=ClusteredConnectorBacklogIT#testClusteredReadQueueAttributesLoadBalancedConnection`); 1 test, 16.27s, pass - Did not run `./mvnw clean install -P contrib-check` (test-only change) -- 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]
