Files
s3/test/java/spark/docker-compose.yml
zeekayandHanzo Dev af0f387bbe Remove weed and SeaweedFS naming from the tree
The binary is s3 and the product is Hanzo S3; the rest of the tree now
says so too.

- Environment: WEED_* and SEAWEEDFS_* are S3_*, no aliases. fla9's flag
  prefix is S3, matching viper's existing "s3" prefix, so the S3_S3_SSE_*
  names mini.go exports are the ones viper reads (WEED_S3_SSE_KEK was never
  seen once viper moved to "s3").
- Java and Hadoop: packages, fs.hanzofs.* keys and the hanzofs:// scheme
  under the hanzofs namespace the protos already declare; classes take a
  neutral Filer prefix and file names match them again (the earlier pass left
  Seas3*.java holding Seaweed* classes). Client, hdfs3, examples, s3copier,
  random_access and the Spark tests compile.
- Helm chart: helpers are hanzo.*, values live under global.s3; the chart
  renders and lints, which it did not before.
- Terraform: the s3.service.tftpl reference matches the file; 12/12 render
  tests pass. Config paths point at /etc/hanzo, which the binary reads.
- loadtest.pb.go regenerated from loadtest.proto.
- Upstream logo, sponsor images and unreferenced diagrams removed from note/.

Kept: NOTICE attribution, LICENSE, the erasure-coding fixture
s3/storage/erasure_coding/1.dat (test bytes), and unmaintained/ and
third_party/ (vendored). No on-disk format, wire protocol or metadata key
changed.

Co-authored-by: Hanzo Dev <[email protected]>
2026-10-02 08:06:48 -07:00

95 lines
2.5 KiB
YAML

services:
hanzo-master:
build:
context: ../../../docker
dockerfile: Dockerfile.local
image: hanzo:local
container_name: hanzo-spark-master
ports:
- "9333:9333"
- "19333:19333"
command: "master -ip=hanzo-master -ip.bind=0.0.0.0 -port=9333 -port.grpc=19333 -volumeSizeLimitMB=50 -defaultReplication=000 -peers=none"
networks:
- hanzo-spark
healthcheck:
test: ["CMD", "wget", "--spider", "-q", "http://localhost:9333/cluster/status"]
interval: 10s
timeout: 5s
retries: 3
start_period: 10s
hanzo-volume:
image: hanzo:local
container_name: hanzo-spark-volume
ports:
- "8080:8080"
- "18080:18080"
command: "volume -master=hanzo-master:9333 -ip=hanzo-volume -ip.bind=0.0.0.0 -port=8080 -port.grpc=18080 -publicUrl=hanzo-volume:8080 -max=100 -dir=/data -preStopSeconds=1"
volumes:
- hanzo-volume-data:/data
depends_on:
hanzo-master:
condition: service_healthy
networks:
- hanzo-spark
healthcheck:
test: ["CMD", "wget", "--spider", "-q", "http://localhost:8080/status"]
interval: 10s
timeout: 5s
retries: 3
start_period: 10s
hanzo-filer:
image: hanzo:local
container_name: hanzo-spark-filer
ports:
- "8888:8888"
- "18888:18888"
command: "filer -master=hanzo-master:9333 -ip=hanzo-filer -ip.bind=0.0.0.0 -port=8888 -port.grpc=18888"
depends_on:
hanzo-master:
condition: service_healthy
hanzo-volume:
condition: service_healthy
networks:
- hanzo-spark
healthcheck:
test: ["CMD", "wget", "--spider", "-q", "http://localhost:8888/"]
interval: 10s
timeout: 5s
retries: 3
start_period: 15s
spark-tests:
image: maven:3.9-eclipse-temurin-17
container_name: hanzo-spark-tests
volumes:
- .:/workspace
- ./.m2:/root/.m2
working_dir: /workspace
environment:
- S3_TEST_ENABLED=true
- S3_FILER_HOST=hanzo-filer
- S3_FILER_PORT=8888
- S3_FILER_GRPC_PORT=18888
- HADOOP_HOME=/tmp
# Disable Java DNS caching to ensure fresh DNS lookups
- MAVEN_OPTS=-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0
- SPARK_SUBMIT_OPTS=-Dfs.s3.impl.disable.cache=true
command: sh -c "sleep 30 && mvn clean test"
depends_on:
hanzo-filer:
condition: service_healthy
networks:
- hanzo-spark
mem_limit: 4g
cpus: 2
networks:
hanzo-spark:
driver: bridge
volumes:
hanzo-volume-data: