My akka cluster node reboot in an unexpected way

Akka Akka Cluster
1

My akka cluster shutdown after giving the following warning

2021-06-22 22:44:27	
06/22 19:44:27.886 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.138.41:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted Show context
2021-06-22 22:44:27	
06/22 19:44:27.885 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.216.76:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.885 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.170.43:25520], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.884 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.242.239:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.883 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.179.71:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.883 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.216.76:25520], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.883 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.138.41:25520], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.883 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.216.65:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.882 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.242.239:25520], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.882 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.239.79:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.882 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.216.65:25520], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.881 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.170.43:25520], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted 
2021-06-22 22:44:27	
06/22 19:44:27.877 WARN [dispatch-actor-system-akka.actor.default-dispatcher-11218] a.s.Materializer - [outbound connection to [akka://dispatch-actor-system@10.235.239.79:25520], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
2

Those warnings means the cluster connections to other nodes got aborted, could be some network infrastructure issue, or the other nodes being abruptly terminated perhaps. This does not in itself shut down the cluster though, but sbr may shut down the node as a consequence, you should have more info in the logs about that around the time this happened.