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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/08/26 18:02:20 UTC
[jira] [Created] (HADOOP-13550) Azure threaded deleter logs too
much at info
Steve Loughran created HADOOP-13550:
---------------------------------------
Summary: Azure threaded deleter logs too much at info
Key: HADOOP-13550
URL: https://issues.apache.org/jira/browse/HADOOP-13550
Project: Hadoop Common
Issue Type: Improvement
Components: fs/azure
Affects Versions: 2.8.0
Reporter: Steve Loughran
The new azure parallel deleter shares too much information in the logs about what is going on
{code}
2016-08-26 18:56:16,461 WARN azure.AzureFileSystemThreadPoolExecutor (AzureFileSystemThreadPoolExecutor.java:executeParallel(150)) - Disabling threads for Delete operation as thread count 0 is <= 1
2016-08-26 18:56:21,424 INFO azure.AzureFileSystemThreadPoolExecutor (AzureFileSystemThreadPoolExecutor.java:executeParallel(235)) - Time taken for Delete operation is: 4963 ms with threads: 0
{code}
# given that thread count of 0 is the default, warn is overkill and misleading
# I (and presumably many other users) don't care about how long something took.
These should both be downgraded to debug
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org