[
https://issues.apache.org/jira/browse/HADOOP-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824261#comment-17824261
]
ASF GitHub Bot commented on HADOOP-19103:
-----------------------------------------
vnhive opened a new pull request, #6615:
URL: https://github.com/apache/hadoop/pull/6615
At present an invalid URL can be supplied as an STS endpoint. It will
attempt to create an STSClient with it and then fail with,
> java.net.UnknownHostException: request session credentials:
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.:
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.: https
* This is inefficient. An invalid URL can be parsed much earlier and can be
failed based on the URL format itself.
* The error message is not very clear and does not indicate a problem in the
URL format.
* In this Jira issue, we attempt to parse the STS URL and fail fast with a
more relevant error message.
Testing
Added a new integration test in ITestS3ATemporaryCredentials and verified
that the existing tests ran fine.
> mvn clean install verify -Dit.test=ITestS3ATemporaryCredentials -Dtest=none
> Add logic for verifying that the STS URL is in the correct format
> -----------------------------------------------------------------
>
> Key: HADOOP-19103
> URL: https://issues.apache.org/jira/browse/HADOOP-19103
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Narayanan Venkateswaran
> Priority: Minor
>
> * At present an invalid URL can be supplied as an STS endpoint. It will
> attempt to create an STSClient with it and then fail with,
> {quote}java.net.UnknownHostException: request session credentials:
> 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.:
> 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.: https
> {quote} * This is inefficient. An invalid URL can be parsed much earlier and
> can be failed based on the URL format itself.
> * The error message is not very clear and does not indicate a problem in the
> URL format.
> * In this Jira issue, we attempt to parse the STS URL and fail fast with a
> more relevant error message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
