[ https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743888#comment-14743888 ]
Dushyanth commented on HADOOP-12350: ------------------------------------ [~cnauroth] Thanks for the input chris. I have added a patch that moves the logging framework to Slf4j. As discussed in the JIRA I have added a private cleanup method inside NativeAzureFileSystem class. To address the comment on AzureNativeFileSystemStore, yes the log statement is specifically for fatal exception that can't be retried again. > WASB Logging: Improve WASB Logging around deletes, reads and writes > ------------------------------------------------------------------- > > Key: HADOOP-12350 > URL: https://issues.apache.org/jira/browse/HADOOP-12350 > Project: Hadoop Common > Issue Type: Improvement > Components: tools > Reporter: Dushyanth > Assignee: Dushyanth > Fix For: 2.8.0 > > Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch, > 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch > > > Logging around the WASB component is very limited and it is disabled by > default. This improvement is created to add logging around Reads, Writes and > Deletes when Azure Storage Exception to capture the blobs that hit the > exception. This information is useful while communicating with the Azure > storage team for debugging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)