markap14 commented on PR #11647:
URL: https://github.com/apache/nifi/pull/11647#issuecomment-5590290480

   [Cursor Grok 4.6] **ubuntu-24.04 Java 21** failed again on [run 
34257346917](https://github.com/apache/nifi/actions/runs/34257346917/job/102166383807),
 but this is unrelated to NIFI-16320.
   
   Failing check: `ubuntu-24.04 Java 21` (system-tests)
   
   ```
   java.lang.RuntimeException:
   Waited up to 60 seconds for all 2 nodes to connect but only 1 nodes 
connected. Node states:
     Node [localhost:5672] Status=DISCONNECTED
     Node [localhost:5671] Status=CONNECTED
        at 
org.apache.nifi.tests.system.NiFiSystemIT.waitForAllNodesConnected(NiFiSystemIT.java:333)
        at 
org.apache.nifi.tests.system.clustering.FlowSynchronizationIT.testReconnectAddsProcessor(FlowSynchronizationIT.java:550)
   ```
   
   From node-1 `nifi-app.log` immediately after `reconnectNode(2)`:
   
   ```
   Requesting that node connect to cluster on behalf of CN=localhost
   Status of localhost:5672 changed from DISCONNECTED ... to CONNECTING
   Ignoring received heartbeat from disconnected node localhost:5672. Node was 
disconnected due to [User Disconnected Node]. Issuing disconnection request.
   Status of localhost:5672 changed from CONNECTING ... to DISCONNECTED
   ```
   
   A heartbeat that left node 2 before the reconnect completed was treated as 
coming from a still-disconnected node, so the coordinator disconnected it 
again. This PR only changes `StandardConnectorNode` working-context 
replacement. Connector clustered tests passed on this head (including 
`ClusteredConnectorTroubleshootingIT`). `FlowSynchronizationIT` is framework 
clustering, not that path.
   
   macos-15 Java 21 is still running on the same workflow, so I will rerun only 
the failed shard once that parent run finishes.


-- 
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]

Reply via email to