hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15278) log s3a at info
Date Wed, 07 Mar 2018 20:32:01 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-15278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-15278:
------------------------------------
    Status: Patch Available  (was: Open)

patch 001; s3a logging is commented out & so gets the global scope; aws is uprated to
info, with the exception of the httpclient. This can log stack traces when it gets errors
its retrying, so can be confusing

> log s3a at info
> ---------------
>
>                 Key: HADOOP-15278
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15278
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>         Attachments: HADOOP-15278-001.patch
>
>
> since it was added, hadoop conf/log4j only logs s3a at ERROR, even though in our test/resources
it logs at info. We do actually log lots of stuff useful when debugging things
> Proposed: drop the log level to INFO here



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message