Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.4.0, 3.4.1
Description
Below is an example:
# hadoop fs -Dfs.s3a.bucket.probe=0 -Dfs.s3a.change.detection.version.required=false -Dfs.s3a.change.detection.mode=none -Dfs.s3a.endpoint=http://some.site:9878 -Dfs.s3a.access.keysome=systest -Dfs.s3a.secret.key=8...1 -Dfs.s3a.endpoint=http://some.site:9878 -Dfs.s3a.path.style.access=true -Dfs.s3a.impl=org.apache.hadoop.fs.s3a.S3AFileSystem -ls -R s3a://bucket1/ 24/09/17 10:47:48 WARN impl.MetricsConfig: Cannot locate configuration: tried hadoop-metrics2-s3a-file-system.properties,hadoop-metrics2.properties 24/09/17 10:47:48 INFO impl.MetricsSystemImpl: Scheduled Metric snapshot period at 10 second(s). 24/09/17 10:47:48 INFO impl.MetricsSystemImpl: s3a-file-system metrics system started 24/09/17 10:47:48 WARN impl.ConfigurationHelper: Option fs.s3a.connection.establish.timeout is too low (5,000 ms). Setting to 15,000 ms instead 24/09/17 10:47:50 WARN s3.S3TransferManager: The provided S3AsyncClient is an instance of MultipartS3AsyncClient, and thus multipart download feature is not enabled. To benefit from all features, consider using S3AsyncClient.crtBuilder().build() instead. drwxrwxrwx - root root 0 2024-09-17 10:47 s3a://bucket1/dir1 24/09/17 10:47:53 INFO impl.MetricsSystemImpl: Stopping s3a-file-system metrics system... 24/09/17 10:47:53 INFO impl.MetricsSystemImpl: s3a-file-system metrics system stopped. 24/09/17 10:47:53 INFO impl.MetricsSystemImpl: s3a-file-system metrics system shutdown complete.
Attachments
Attachments
Issue Links
- links to