markap14 commented on PR #10020: URL: https://github.com/apache/nifi/pull/10020#issuecomment-2972830717
@joewitt I agree. They are unrelated, but they need to be analyzed. Looks like 2 system test failures. The first one appears to actually be a threading bug that is unrelated, but I filed a Jira for it (https://issues.apache.org/jira/browse/NIFI-14663) and posted a PR for it. Logs for the other one indicate that it was waiting for Node 2 to rejoin the cluster, but for some reason that is very not clear in the logs, Node 2 was shutdown: ``` 2025-06-13 21:29:08,275 INFO [ShutdownCommand] org.apache.nifi.runtime.command.ShutdownCommand Application shutdown started 2025-06-13 21:29:08,275 INFO [ShutdownCommand] org.apache.nifi.runtime.StandardManagementServer Management Server stopped 2025-06-13 21:29:08,276 INFO [ShutdownCommand] org.eclipse.jetty.server.Server Stopped oejs.Server@3a543f31{STOPPING}[12.0.22,sto=0] 2025-06-13 21:29:08,278 INFO [ShutdownCommand] org.eclipse.jetty.server.AbstractConnector Stopped ServerConnector@386643e{SSL, (ssl, alpn, h2, http/1.1)}{localhost:5672} 2025-06-13 21:29:08,292 INFO [ShutdownCommand] org.eclipse.jetty.ee10.servlet.ServletContextHandler Stopped oeje10w.WebAppContext@566bea82{/nifi,/nifi,b=null,a=AVAILABLE,h=oeje10s.SessionHandler@78026a45{STOPPED}}{./work/nar/extensions/nifi-server-nar-2.5.0-SNAPSHOT.nar-unpacked/NAR-INF/bundled-dependencies/nifi-ui-2.5.0-SNAPSHOT.war} 2025-06-13 21:29:08,297 INFO [ShutdownCommand] org.apache.nifi.web.contextlistener.ApplicationStartupContextListener Flow Service shutdown started 2025-06-13 21:29:08,297 INFO [ShutdownCommand] org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator Status of localhost:5672 changed from NodeConnectionStatus[nodeId=localhost:5672, state=CONNECTED, updateId=17] to NodeConnectionStatus[nodeId=localhost:5672, state=DISCONNECTED, Disconnect Code=Node was Shutdown, Disconnect Reason=Node was Shutdown, updateId=17] ``` And so it never rejoined the cluster. I looked through the logs and could find nothing at all indicating that it was being shutdown. So perhaps something wonky like the VM that it was running on was out of memory and as a result sent a `kill` command to the Process? Nothing else makes sense to me, because I could not find any logs indicating that it was being shutdown intentionally. That said, I re-ran the system tests run to ensure that all pass this time. -- 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-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
