[ 
https://issues.apache.org/jira/browse/HADOOP-15278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390131#comment-16390131
 ] 

Steve Loughran commented on HADOOP-15278:
-----------------------------------------

Nope, nothing by default

{code}
bin/hadoop fs -ls s3a://hwdev-steve-london/
Found 1 items
drwxrwxrwx   - stevel stevel          0 2018-03-07 20:12 
s3a://hwdev-steve-london/Users
{code}

you do get more on other ops, like committing work, which is where I'd like it

> 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to