You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In some deployments of storage systems implementing the S3 API, the default "virtual path" style for request URLs does not work, as it may induce problems related to DNS. In these cases, the "path-style" URLs may be working fine, so it would be interesting to be able to configure the style of URLs for S3 biding as a parameter.
To Reproduce
Using "virtual-path" on a cluster with a storage system implementing S3 APIs, I got the following issue:
Caused by: software.amazon.awssdk.core.exception.SdkClientException: Received an UnknownHostException when attempting to interact with a service. See cause for the exact endpoint that is failing to resolve. If this is happening on an endpoint that previously worked, there may be a network connectivity issue or your DNS cache could be storing endpoints for too long.
at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:98)
...
... 5 common frames omitted
Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: [BUCKET_NAME].[STORAGE_SERVER_NAME]
at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:98)
After modifying the S3 binding configuration to use "path-style" requests, Pravega was able to run correctly.
Screenshots
n/a
Additional information
A solution would be just adding something like this in the S3 binding configuration:
Describe the bug
In some deployments of storage systems implementing the S3 API, the default "virtual path" style for request URLs does not work, as it may induce problems related to DNS. In these cases, the "path-style" URLs may be working fine, so it would be interesting to be able to configure the style of URLs for S3 biding as a parameter.
To Reproduce
Using "virtual-path" on a cluster with a storage system implementing S3 APIs, I got the following issue:
After modifying the S3 binding configuration to use "path-style" requests, Pravega was able to run correctly.
Screenshots
n/a
Additional information
A solution would be just adding something like this in the S3 binding configuration:
Where
enablePathStyleAccess
is a configurable parameter (deafulted tofalse
as it is today).The text was updated successfully, but these errors were encountered: