[ https://issues.apache.org/jira/browse/HADOOP-18999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-18999. ------------------------------------- Resolution: Not A Problem no longer needed as 2.21.41 logs properly! > S3A: debug logging for http traffic to S3 stores > ------------------------------------------------ > > Key: HADOOP-18999 > URL: https://issues.apache.org/jira/browse/HADOOP-18999 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.4.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Major > Labels: pull-request-available > > AWS SDK bundle.jar logging doesn't set up right. > {code} > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > {code} > Cloudstore commands have a -debug option to force set this through log4j > APIs; this does work. > Proposed: > * add reflection-based ability to set/query log4j log levels (+tests, > obviously) > * add a new log `org.apache.hadoop.fs.s3a.logging.sdk` > * if set to DEBUG, DefaultS3ClientFactory will enable logging on the aws > internal/shaded classes > this allows log4j.properties to turn on logging; reflection ensures all is > well on other log back-ends and when unshaded aws sdk jars are in use -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org