What happened?
On a fresh texera_start, FileService.run creates the dataset and large-binary buckets via S3StorageClient.createBucketIfNotExist(...) (FileService.scala:79, 81) with no retry. If MinIO/S3 has not finished starting, headBucket/createBucket throws an S3Exception and aborts file-service startup before it can serve requests. The sibling LakeFSStorageClient.healthCheck() was already hardened with retry/backoff in #5647, but the two bucket-creation calls were left unguarded.
How to reproduce?
- Start a fresh deployment where the object store (MinIO/S3) comes up slower than file-service, e.g.
texera_start on a cold machine or slow container start.
- Observe file-service throw an
S3Exception out of createBucketIfNotExist during startup and exit instead of waiting for the dependency.
Version/Branch
main, as of 2026-06-21.
What happened?
On a fresh
texera_start,FileService.runcreates the dataset and large-binary buckets viaS3StorageClient.createBucketIfNotExist(...)(FileService.scala:79, 81) with no retry. If MinIO/S3 has not finished starting,headBucket/createBucketthrows anS3Exceptionand aborts file-service startup before it can serve requests. The siblingLakeFSStorageClient.healthCheck()was already hardened with retry/backoff in #5647, but the two bucket-creation calls were left unguarded.How to reproduce?
texera_starton a cold machine or slow container start.S3Exceptionout ofcreateBucketIfNotExistduring startup and exit instead of waiting for the dependency.Version/Branch
main, as of 2026-06-21.