[
https://issues.apache.org/jira/browse/HDDS-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851952#comment-17851952
]
Tejaskriya Madhan commented on HDDS-7018:
-----------------------------------------
Trailing slash needed for bucket access is a behaviour related to S3A
filesystem and not specific to Ozone. The behaviour should be same if s3a is
used across Ozone/hadoop or AWS environments.
If we do not provide the trailing slash, the S3A client code appends the path
with /user/username and since this path doesn't exist in Ozone we get 'No such
file or directory'.
cc [~sshenoy]
> trailing slash should not be needed for s3 access
> -------------------------------------------------
>
> Key: HDDS-7018
> URL: https://issues.apache.org/jira/browse/HDDS-7018
> Project: Apache Ozone
> Issue Type: Bug
> Components: S3
> Reporter: George Huang
> Assignee: Tejaskriya Madhan
> Priority: Major
>
> If trailing slash is not specified, it is not possible to access s3.
> *Without trailing slash:*
> [root@vc0802 ~]# hadoop fs -ls -R s3a://testbucket
> 22/07/19 09:02:17 WARN impl.MetricsConfig: Cannot locate configuration: tried
> hadoop-metrics2-s3a-file-system.properties,hadoop-metrics2.properties
> 22/07/19 09:02:17 INFO impl.MetricsSystemImpl: Scheduled Metric snapshot
> period at 10 second(s).
> 22/07/19 09:02:17 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> started
> 22/07/19 09:02:18 INFO Configuration.deprecation: No unit for
> fs.s3a.connection.request.timeout(0) assuming SECONDS
> *ls: `s3a://testbucket': No such file or directory*
> 22/07/19 09:02:18 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
> metrics system...
> 22/07/19 09:02:18 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> stopped.
> 22/07/19 09:02:18 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> shutdown complete.
> *With trailing slash:*
> [root@vc0802 ~]# hadoop fs -ls -R s3a://testbucket/
> 22/07/19 09:07:39 WARN impl.MetricsConfig: Cannot locate configuration: tried
> hadoop-metrics2-s3a-file-system.properties,hadoop-metrics2.properties
> 22/07/19 09:07:39 INFO impl.MetricsSystemImpl: Scheduled Metric snapshot
> period at 10 second(s).
> *22/07/19 09:07:39 INFO impl.MetricsSystemImpl: s3a-file-system metrics
> system started*
> *22/07/19 09:07:39 INFO Configuration.deprecation: No unit for
> fs.s3a.connection.request.timeout(0) assuming SECONDS*
> *drwxrwxrwx - systest systest 0 2022-07-19 09:07
> s3a://testbucket/dir1*
> *drwxrwxrwx - systest systest 0 2022-07-19 09:07
> s3a://testbucket/dir1/dir2*
> 22/07/19 09:07:40 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
> metrics system...
> 22/07/19 09:07:40 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> stopped.
> 22/07/19 09:07:40 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> shutdown complete.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
