john8628 opened a new issue, #4154:
URL: https://github.com/apache/incubator-seatunnel/issues/4154

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   i follow the lastest dev , run seatunnel-cluster.sh with this problem ; ( 
seatunnel-cluster.sh  add  java_opts, and hazelcast-client.yaml  add cluster 
member),
   
   ### SeaTunnel Version
   
   dev
   
   ### SeaTunnel Config
   
   ```conf
   hazelcast-client.yaml
   #
   # Licensed to the Apache Software Foundation (ASF) under one or more
   # contributor license agreements.  See the NOTICE file distributed with
   # this work for additional information regarding copyright ownership.
   # The ASF licenses this file to You under the Apache License, Version 2.0
   # (the "License"); you may not use this file except in compliance with
   # the License.  You may obtain a copy of the License at
   #
   #    http://www.apache.org/licenses/LICENSE-2.0
   #
   # Unless required by applicable law or agreed to in writing, software
   # distributed under the License is distributed on an "AS IS" BASIS,
   # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   # See the License for the specific language governing permissions and
   # limitations under the License.
   #
   
   hazelcast:
     cluster-name: seatunnel
     advanced-network:
       enabled: true
       member-server-socket-endpoint-config:
         port:
           auto-increment: true
           port-count: 100
           port: 9000
       client-server-socket-endpoint-config:
         port:
           auto-increment: true
           port-count: 100
           port: 5801
       rest-server-socket-endpoint-config:
         port:
           auto-increment: true
           port-count: 100
           port: 8080
         endpoint-groups:
           WAN:
             enabled: true
           CLUSTER_READ:
             enabled: true
           HEALTH_CHECK:
             enabled: true
       join:
         tcp-ip:
           enabled: true
           member-list:
             - localhost
     properties:
       hazelcast.invocation.max.retry.count: 20
       hazelcast.tcp.join.port.try.count: 30
       hazelcast.logging.type: log4j2
   
   hazelcast-client.yaml
   
   hazelcast-client:
     cluster-name: seatunnel
     properties:
       hazelcast.logging.type: log4j2
     network:
       cluster-members:
         - 10.*:5801
         - 10.*:5801
         - 10.*:5801
   ```
   
   
   ### Running Command
   
   ```shell
   bash seatunnel-cluster.sh
   ```
   
   
   ### Error Exception
   
   ```log
   23-02-17 10:08:01,902 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (8/20) after backoff of 1000 ms
   2023-02-17 10:08:02,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:02,903 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (9/20) after backoff of 1000 ms
   2023-02-17 10:08:03,903 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (10/20) after backoff of 1000 ms
   2023-02-17 10:08:04,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:04,903 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (11/20) after backoff of 1000 ms
   2023-02-17 10:08:05,903 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (12/20) after backoff of 1000 ms
   2023-02-17 10:08:06,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:06,903 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (13/20) after backoff of 1000 ms
   2023-02-17 10:08:07,904 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (14/20) after backoff of 1000 ms
   2023-02-17 10:08:08,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:08,904 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (15/20) after backoff of 1000 ms
   2023-02-17 10:08:09,904 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (16/20) after backoff of 1000 ms
   2023-02-17 10:08:10,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:10,904 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (17/20) after backoff of 1000 ms
   2023-02-17 10:08:11,904 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (18/20) after backoff of 1000 ms
   2023-02-17 10:08:12,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:12,905 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (19/20) after backoff of 1000 ms
   2023-02-17 10:08:13,905 WARN  org.apache.seatunnel.common.utils.RetryUtils - 
Failed to execute due to null. Retrying attempt (20/20) after backoff of 1000 ms
   2023-02-17 10:08:14,892 WARN  
org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed 
send heartbeat to resource manager, will retry later. this address: 
[localhost]:9000
   2023-02-17 10:08:14,906 ERROR 
org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:9000 
[seatunnel_default_cluster] [5.1] 
org.apache.seatunnel.engine.common.exception.SeaTunnelEngineException: cluster 
have no master node
        at 
org.apache.seatunnel.engine.server.SeaTunnelServer.isMasterNode(SeaTunnelServer.java:236)
        at 
org.apache.seatunnel.engine.server.CoordinatorService.checkNewActiveMaster(CoordinatorService.java:335)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
   Caused by: java.lang.RuntimeException: Execute given execution failed after 
retry 20 times
        at 
org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:70)
        at 
org.apache.seatunnel.engine.server.SeaTunnelServer.isMasterNode(SeaTunnelServer.java:225)
   ```
   
   
   ### 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