Files
seaweedfs/test
chrislu ce40e2fd58 fix: use container hostname for volume server to enable automatic volume creation
Root cause identified:
- Volume server was using -ip=127.0.0.1
- Master couldn't reach volume server at 127.0.0.1 from its container
- When Spark requested assignment, master tried to create volume via gRPC
- Master's gRPC call to 127.0.0.1:18080 failed (reached itself, not volume server)
- Result: 'No writable volumes' error

Solution:
- Change volume server to use -ip=seaweedfs-volume (container hostname)
- Master can now reach volume server at seaweedfs-volume:18080
- Automatic volume creation works as designed
- Kept -publicUrl=127.0.0.1:8080 for external clients (host network)

Workflow changes:
- Remove forced volume creation (curl POST to /vol/grow)
- Volumes will be created automatically on first write request
- Keep diagnostic output for troubleshooting
- Simplified startup verification

This matches how other SeaweedFS tests work with Docker networking.
2025-11-22 23:09:27 -08:00
..
2025-11-18 12:06:56 -08:00
2025-11-18 12:06:56 -08:00
2025-11-22 12:38:45 -08:00
2025-10-13 18:05:17 -07:00
2025-11-18 12:06:56 -08:00
2023-11-13 08:23:53 -08:00