Skip to content

Running a workflow triggers S3 NoSuchBucketException for 'texera-large-binaries' #4239

@mengw15

Description

@mengw15

What happened?

When initializing a workflow execution, the system attempts to clear execution resources via WorkflowService.clearExecutionResources. This triggers LargeBinaryManager.deleteAllObjects which tries to delete files from the S3 bucket named texera-large-binaries.

However, a warning is thrown because the bucket does not exist, resulting in a NoSuchBucketException.

Error Log:

[2026-02-18 23:38:39,769] [WARN] [org.apache.texera.service.util.LargeBinaryManager$] [dw-36] - Failed to delete large binaries from bucket: texera-large-binaries
software.amazon.awssdk.services.s3.model.NoSuchBucketException: The specified bucket does not exist (Service: S3, Status Code: 404, Request ID: 18957B97A8256FDF, Extended Request ID: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8)
at software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:155)
...
at org.apache.texera.service.util.S3StorageClient$.deleteDirectory(S3StorageClient.scala:114)
at org.apache.texera.service.util.LargeBinaryManager$.deleteAllObjects(LargeBinaryManager.scala:58)
at org.apache.texera.web.service.WorkflowService.clearExecutionResources(WorkflowService.scala:352)
at org.apache.texera.web.service.WorkflowService.$anonfun$initExecutionService$2(WorkflowService.scala:202)
...

How to reproduce?

Executing workflow

Version

1.1.0-incubating (Pre-release/Master)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

No response

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    triagePending for triaging

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions