[
https://issues.apache.org/jira/browse/HADOOP-18999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792921#comment-17792921
]
ASF GitHub Bot commented on HADOOP-18999:
-----------------------------------------
steveloughran opened a new pull request, #6322:
URL: https://github.com/apache/hadoop/pull/6322
Aims to set debug logging of http messages if the log
org.apache.hadoop.fs.s3a.logging.sdk is set to debug.
```properties
# AWS v2 low level logging
log4j.logger.org.apache.hadoop.fs.s3a.logging.sdk=DEBUG
```
This doesn't work in production, even though it's based on the cloudstore
StoreEntryPoint code which does. No idea why not
### How was this patch tested?
* new test to show logs can be changed
* running some itests doesn't show new value
* nor does CLI
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
