jianchengwang opened a new issue, #7434:
URL: https://github.com/apache/seatunnel/issues/7434

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   when i start the worker node, the disk io full, and the system block can't 
do anything must to restart system, here are logs
   
   ```
   2024-08-14 16:57:31,489 INFO  [c.h.s.security                ] [main] - 
[localhost]:5828 [seatunnel-349349] [5.1] Enable DEBUG/FINE log level for log 
category com.hazelcast.system.security  or use 
-Dhazelcast.security.recommendations system property to see 🔒 security 
recommendations and the status of current config.
   [INFO] 2024-08-14 16:57:31.598 +0800 
org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[181] - 
[WorkflowInstance-0][TaskInstance-0] -  -> 
        2024-08-14 16:57:30,703 INFO  [c.h.s.security                ] [main] - 
[localhost]:5832 [seatunnel-572113] [5.1] Enable DEBUG/FINE log level for log 
category com.hazelcast.system.security  or use 
-Dhazelcast.security.recommendations system property to see 🔒 security 
recommendations and the status of current config.
   [INFO] 2024-08-14 16:57:31.640 +0800 
org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[181] - 
[WorkflowInstance-0][TaskInstance-0] -  -> 
        2024-08-14 16:57:30,662 INFO  [c.h.i.d.Diagnostics           ] [main] - 
[localhost]:5812 [seatunnel-42883] [5.1] Diagnostics disabled. To enable add 
-Dhazelcast.diagnostics.enabled=true to the JVM arguments.
        2024-08-14 16:57:30,686 INFO  [c.h.c.LifecycleService        ] [main] - 
[localhost]:5812 [seatunnel-42883] [5.1] [localhost]:5812 is STARTING
   [INFO] 2024-08-14 16:57:31.670 +0800 
org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[181] - 
[WorkflowInstance-0][TaskInstance-0] -  -> 
        2024-08-14 16:57:30,745 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-2] - [localhost]:5809 [seatunnel-223591] [5.1] 
Initialized new cluster connection between /127.0.0.1:5809 and /127.0.0.1:42763
        2024-08-14 16:57:30,745 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-1] - [localhost]:5809 [seatunnel-223591] [5.1] 
Initialized new cluster connection between /127.0.0.1:40301 and 
localhost/127.0.0.1:5810
        2024-08-14 16:57:30,815 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-1] - [localhost]:5809 [seatunnel-223591] [5.1] 
Initialized new cluster connection between /127.0.0.1:50623 and 
localhost/127.0.0.1:5802
        2024-08-14 16:57:31,540 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-2] - [localhost]:5809 [seatunnel-223591] [5.1] 
Initialized new cluster connection between /127.0.0.1:51177 and 
localhost/127.0.0.1:5807
   [INFO] 2024-08-14 16:57:31.670 +0800 
org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[181] - 
[WorkflowInstance-0][TaskInstance-0] -  -> 
        2024-08-14 16:57:30,811 WARN  [c.h.i.c.i.ClusterJoinManager  ] 
[hz.main.priority-generic-operation.thread-0] - [localhost]:5808 
[seatunnel-310231] [5.1] Received an invalid join request from 
[localhost]:5806, cause: members part of different cluster
        2024-08-14 16:57:30,813 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-2] - [localhost]:5808 [seatunnel-310231] [5.1] 
Initialized new cluster connection between /127.0.0.1:5808 and /127.0.0.1:37967
        2024-08-14 16:57:30,815 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-0] - [localhost]:5808 [seatunnel-310231] [5.1] 
Initialized new cluster connection between /127.0.0.1:52927 and 
localhost/127.0.0.1:5809
        2024-08-14 16:57:30,866 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-1] - [localhost]:5808 [seatunnel-310231] [5.1] 
Initialized new cluster connection between /127.0.0.1:49819 and 
localhost/127.0.0.1:5810
        2024-08-14 16:57:30,871 WARN  [c.h.i.c.i.ClusterJoinManager  ] 
[hz.main.generic-operation.thread-7] - [localhost]:5808 [seatunnel-310231] 
[5.1] Received an invalid join request from [localhost]:5802, cause: members 
part of different cluster
        2024-08-14 16:57:31,566 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-1] - [localhost]:5808 [seatunnel-310231] [5.1] 
Initialized new cluster connection between /127.0.0.1:39073 and 
localhost/127.0.0.1:5805
        2024-08-14 16:57:31,576 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-0] - [localhost]:5808 [seatunnel-310231] [5.1] 
Initialized new cluster connection between /127.0.0.1:5808 and /127.0.0.1:44747
        2024-08-14 16:57:31,621 WARN  [c.h.i.c.i.ClusterJoinManager  ] 
[hz.main.priority-generic-operation.thread-0] - [localhost]:5808 
[seatunnel-310231] [5.1] Received an invalid join request from 
[localhost]:5806, cause: members part of different cluster
   [INFO] 2024-08-14 16:57:31.685 +0800 
org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[181] - 
[WorkflowInstance-0][TaskInstance-0] -  -> 
        2024-08-14 16:57:30,790 INFO  [c.h.i.s.t.TcpServerConnection ] 
[hz.main.IO.thread-in-1] - [localhost]:5802 [seatunnel-561177] [5.1] 
Initialized new cluster connection between /127.0.0.1:49861 and 
localhost/127.0.0.1:5809
   ```
   
   ### SeaTunnel Version
   
   3.2.0
   
   ### SeaTunnel Config
   
   ```conf
   none
   ```
   
   
   ### Running Command
   
   ```shell
   none
   ```
   
   
   ### Error Exception
   
   ```log
   none
   ```
   
   
   ### Zeta or Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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