You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Dushyanth (JIRA)" <ji...@apache.org> on 2015/09/14 19:36:46 UTC
[jira] [Updated] (HADOOP-12350) WASB Logging: Improve WASB Logging
around deletes, reads and writes
[ https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dushyanth updated HADOOP-12350:
-------------------------------
Attachment: 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch
Adding patch that changes to slf4j logging framework.
> 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)