[ 
https://issues.apache.org/jira/browse/NIFI-16562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143882#comment-18143882
 ] 

ASF subversion and git services commented on NIFI-16562:
--------------------------------------------------------

Commit 0b218b026db9ffe03f728334b01b13910da7b46b in nifi's branch 
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0b218b026db ]

NIFI-16562 - Fix flaky ClusteredStopSourcesIT and 
ClusteredConnectorAutoResumeIT (#11897)

Signed-off-by: David Handermann <[email protected]>

> Fix flaky ClusteredStopSourcesIT and ClusteredConnectorAutoResumeIT
> -------------------------------------------------------------------
>
>                 Key: NIFI-16562
>                 URL: https://issues.apache.org/jira/browse/NIFI-16562
>             Project: Apache NiFi
>          Issue Type: Test
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Several clustered system tests fail intermittently in CI for reasons 
> unrelated to the changes under test.
>  * 
> {*}ClusteredStopSourcesIT{*}: Processors in a Stateless Process Group are 
> started asynchronously on each node. The test waits on the cluster-replicated 
> processor state, which does not merge the component state across nodes, so 
> the wait can complete while one node still reports STOPPED. The test now 
> waits on each node directly. A reusable {{waitForOnAllNodes}} helper is added 
> to {{{}NiFiSystemIT{}}}.
>  * 
> {*}ClusteredConnectorAutoResumeIT{*}: A node restart failed with 
> {{BindException}} on the cluster protocol port (48102). Ports 48101/48102 
> fall within the default Linux ephemeral port range, so an outbound connection 
> can take the port. The test cluster's protocol ports move to 6351/6352. 
> Separately, the test framework kept waiting on a node that had already exited 
> until the 5-minute test timeout. Startup now fails as soon as the node 
> process exits, and {{AggregateNiFiInstance}} rethrows startup failures from 
> its startup threads instead of dropping them.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to