turbo-one-off opened a new issue, #10883:
URL: https://github.com/apache/seatunnel/issues/10883

   ### 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
   
   Configured `map.engine*.map-store` in `seatunnel.yaml` per the [official 
Separated Cluster Mode 
doc](https://seatunnel.apache.org/docs/2.3.13/engines/zeta/separated-cluster-deployment/)
 using `FileMapStoreFactory` with `file:///` backend. The configuration is 
**silently ignored** — no error log, no file written, no IMap persistence. 
After integer cluster restart, all previously RUNNING jobs are lost 
(`running-jobs` returns `[]`).
   
   Root cause (after investigation): **`imap-storage-file` plugin jar is not 
packaged in the binary release**. The Maven assembly descriptor 
`seatunnel-dist/src/main/assembly/assembly-bin-ci.xml` does not reference any 
`imap-storage` artifact, and `tar tzf apache-seatunnel-2.3.13-bin.tar.gz | grep 
-i imap-storage` returns empty. The source module exists at 
`seatunnel-engine/seatunnel-engine-storage/imap-storage-plugins/imap-storage-file/`
 and the artifact `org.apache.seatunnel:imap-storage-file:2.3.13` is published 
to Maven Central, but the binary release ships without it.
   
   Manually copying the jar to `/opt/seatunnel/lib/` is not enough — SeaTunnel 
does not pick it up at runtime (presumably classpath/SPI wiring difference 
between `lib/` and a dedicated `plugins/imap-storage-plugins/` subdirectory 
which doesn't exist in the release).
   
   ### SeaTunnel Version
   
   2.3.13 (also reproducible in 2.3.9 per #8733 — long-standing)
   
   
   ### SeaTunnel Config
   
   ```conf
   # seatunnel.yaml (master role, per official doc)
   seatunnel:
     engine:
       backup-count: 2
       http:
         enable-http: true
         port: 8080
   
   map:
     engine*:
       map-store:
         enabled: true
         initial-mode: EAGER
         factory-class-name: 
org.apache.seatunnel.engine.server.persistence.FileMapStoreFactory
         properties:
           type: hdfs
           namespace: /tmp/seatunnel/imap
           clusterName: seatunnel-cluster
           storage.type: hdfs
           fs.defaultFS: file:///
   ```
   
   ### Running Command
   
   ```shell
   ./bin/seatunnel-cluster.sh -r master    # 3 master nodes
   ./bin/seatunnel-cluster.sh -r worker    # 2 worker nodes
   ./bin/seatunnel.sh --config /tmp/fake_streaming.conf -e cluster --async 
--name fake-ha-test
   ```
   
   ### Error Exception
   
   ```log
   No exception. **Silent failure** — no MapStore-related log entries, no files 
in `/tmp/seatunnel/imap`. After `docker compose down + up` (whole cluster 
restart), `curl localhost:8080/running-jobs` returns `[]` instead of recovering 
the previously submitted job.
   ```
   
   ### Zeta or Flink or Spark Version
   
   Zeta (separated cluster mode, 3 master + 2 worker)
   
   
   ### Java or Scala Version
   
   OpenJDK 1.8.0_342 (apache/seatunnel:2.3.13 official image)
   
   
   ### Screenshots
   
   ```
   # Evidence binary release ships without the plugin:
   $ tar tzf apache-seatunnel-2.3.13-bin.tar.gz | grep -iE "imap|storage" | head
   (empty)
   
   # Assembly descriptor doesn't reference imap-storage:
   $ grep -i "imap-storage" seatunnel-dist/src/main/assembly/assembly-bin-ci.xml
   (empty)
   
   # Plugin source exists:
   $ ls seatunnel-engine/seatunnel-engine-storage/imap-storage-plugins/
   imap-storage-file  pom.xml
   
   # Maven Central has the artifact:
   $ curl -sI 
https://repo1.maven.org/maven2/org/apache/seatunnel/imap-storage-file/2.3.13/imap-storage-file-2.3.13.jar
   HTTP/1.1 200 OK
   ```
   
   ### 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