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

   ### 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
   
   According to the official website deployment of separated cluster 
deployment, after configuring Imap, neither local files nor HDFS files were 
created in the Imap directory
   
   ### SeaTunnel Version
   
   2.3.6 and dev
   
   ### SeaTunnel Config
   
   ```conf
   hazelcast.yaml
   hazelcast:
     cluster-name: seatunnel
     network:
       rest-api:
         enabled: true
         endpoint-groups:
           CLUSTER_WRITE:
             enabled: true
           DATA:
             enabled: true
       join:
         tcp-ip:
           enabled: true
           member-list:
             - localhost
       port:
         auto-increment: false
         port: 5801
     properties:
       hazelcast.invocation.max.retry.count: 20
       hazelcast.tcp.join.port.try.count: 30
       hazelcast.logging.type: log4j2
       hazelcast.operation.generic.thread.count: 50
       hazelcast.heartbeat.failuredetector.type: phi-accrual
       hazelcast.heartbeat.interval.seconds: 2
       hazelcast.max.no.heartbeat.seconds: 180
       hazelcast.heartbeat.phiaccrual.failuredetector.threshold: 10
       hazelcast.heartbeat.phiaccrual.failuredetector.sample.size: 200
       hazelcast.heartbeat.phiaccrual.failuredetector.min.std.dev.millis: 100
     map:
       engine*:
         map-store:
           enabled: true
           initial-mode: EAGER
           factory-class-name: 
org.apache.seatunnel.engine.server.persistence.FileMapStoreFactory
           properties:
             type: hdfs
             namespace: /opt/module/seatunnel/imap
             clusterName: seatunnel
             storage.type: hdfs
            # fs.defaultFS: hdfs://172.16.11.151:8020
             fs.defaultFS: file:///
   
   hazelcast-master.yaml
   hazelcast:
     cluster-name: seatunnel
     network:
       rest-api:
         enabled: true
         endpoint-groups:
           CLUSTER_WRITE:
             enabled: true
           DATA:
             enabled: true
       join:
         tcp-ip:
           enabled: true
           member-list:
             - 172.16.11.151:5801
             - 172.16.11.151:5802
             - 172.16.11.152:5802
             - 172.16.11.153:5802
       port:
         auto-increment: false
         port: 5801
     properties:
       hazelcast.invocation.max.retry.count: 20
       hazelcast.tcp.join.port.try.count: 30
       hazelcast.logging.type: log4j2
       hazelcast.operation.generic.thread.count: 50
       hazelcast.heartbeat.failuredetector.type: phi-accrual
       hazelcast.heartbeat.interval.seconds: 2
       hazelcast.max.no.heartbeat.seconds: 180
       hazelcast.heartbeat.phiaccrual.failuredetector.threshold: 10
       hazelcast.heartbeat.phiaccrual.failuredetector.sample.size: 200
       hazelcast.heartbeat.phiaccrual.failuredetector.min.std.dev.millis: 100
   ```
   
   
   ### Running Command
   
   ```shell
   bin/seatunnel-cluster.sh -d -r master
   ```
   
   
   ### Error Exception
   
   ```log
   imap config not effective
   ```
   
   
   ### Zeta or Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   1.8
   
   ### Screenshots
   
   
![image](https://github.com/user-attachments/assets/9a893ef4-66b6-422a-b3c8-25970b793923)
   
![image](https://github.com/user-attachments/assets/bc47bfce-de6e-4d96-93f6-648bc8a34d83)
   
   
   ### Are you willing to submit PR?
   
   - [X] 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