[
https://issues.apache.org/jira/browse/HADOOP-17801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mehakmeet Singh updated HADOOP-17801:
-------------------------------------
Description:
No error message is shown at INFO level, when the bucket trying to access,
doesn't exist.
While translating the exception when the bucket doesn't exist(error code:
NoSuchBucket, status code: 404), we are setting the "path" as the error message
rather than "message", the actual error message.
for eg:
{code:java}
❯ bin/hadoop fs -ls s3a://mmt-no-bucket/
2021-07-14 12:58:26,169 WARN util.NativeCodeLoader: Unable to load
native-hadoop library for your platform... using builtin-java classes where
applicable
2021-07-14 12:58:26,392 INFO impl.MetricsConfig: Loaded properties from
hadoop-metrics2.properties
2021-07-14 12:58:26,448 INFO impl.MetricsSystemImpl: Scheduled Metric snapshot
period at 10 second(s).
2021-07-14 12:58:26,448 INFO impl.MetricsSystemImpl: s3a-file-system metrics
system started
ls: s3a://mmt-no-bucket/
2021-07-14 12:58:27,712 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
metrics system...
2021-07-14 12:58:27,713 INFO impl.MetricsSystemImpl: s3a-file-system metrics
system stopped.
2021-07-14 12:58:27,713 INFO impl.MetricsSystemImpl: s3a-file-system metrics
system shutdown complete. {code}
was:
No error message is shown at INFO level, when the bucket trying to access,
doesn't exist.
While translating the exception, we are setting the "path" as the error message
rather than "message", the actual error message.
for eg:
{code:java}
❯ bin/hadoop fs -ls s3a://mmt-no-bucket/
2021-07-14 12:58:26,169 WARN util.NativeCodeLoader: Unable to load
native-hadoop library for your platform... using builtin-java classes where
applicable
2021-07-14 12:58:26,392 INFO impl.MetricsConfig: Loaded properties from
hadoop-metrics2.properties
2021-07-14 12:58:26,448 INFO impl.MetricsSystemImpl: Scheduled Metric snapshot
period at 10 second(s).
2021-07-14 12:58:26,448 INFO impl.MetricsSystemImpl: s3a-file-system metrics
system started
ls: s3a://mmt-no-bucket/
2021-07-14 12:58:27,712 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
metrics system...
2021-07-14 12:58:27,713 INFO impl.MetricsSystemImpl: s3a-file-system metrics
system stopped.
2021-07-14 12:58:27,713 INFO impl.MetricsSystemImpl: s3a-file-system metrics
system shutdown complete. {code}
> No error message reported when bucket doesn't exist in S3AFS
> ------------------------------------------------------------
>
> Key: HADOOP-17801
> URL: https://issues.apache.org/jira/browse/HADOOP-17801
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Mehakmeet Singh
> Assignee: Mehakmeet Singh
> Priority: Major
>
> No error message is shown at INFO level, when the bucket trying to access,
> doesn't exist.
> While translating the exception when the bucket doesn't exist(error code:
> NoSuchBucket, status code: 404), we are setting the "path" as the error
> message rather than "message", the actual error message.
> for eg:
> {code:java}
> ❯ bin/hadoop fs -ls s3a://mmt-no-bucket/
> 2021-07-14 12:58:26,169 WARN util.NativeCodeLoader: Unable to load
> native-hadoop library for your platform... using builtin-java classes where
> applicable
> 2021-07-14 12:58:26,392 INFO impl.MetricsConfig: Loaded properties from
> hadoop-metrics2.properties
> 2021-07-14 12:58:26,448 INFO impl.MetricsSystemImpl: Scheduled Metric
> snapshot period at 10 second(s).
> 2021-07-14 12:58:26,448 INFO impl.MetricsSystemImpl: s3a-file-system metrics
> system started
> ls: s3a://mmt-no-bucket/
> 2021-07-14 12:58:27,712 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
> metrics system...
> 2021-07-14 12:58:27,713 INFO impl.MetricsSystemImpl: s3a-file-system metrics
> system stopped.
> 2021-07-14 12:58:27,713 INFO impl.MetricsSystemImpl: s3a-file-system metrics
> system shutdown complete. {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
