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 2019/11/13 17:45:00 UTC
[jira] [Created] (HADOOP-16708) HadoopExecutors cleanup to only log
at debug
Steve Loughran created HADOOP-16708:
---------------------------------------
Summary: HadoopExecutors cleanup to only log at debug
Key: HADOOP-16708
URL: https://issues.apache.org/jira/browse/HADOOP-16708
Project: Hadoop Common
Issue Type: Improvement
Components: util
Affects Versions: 3.3.0
Reporter: Steve Loughran
HadoopExecutors cleanup to only log at debug
HADOOP-16181 means that executor shutdown now logs @ info
this means every single hadoop fs command against s3 has four lines of information which is entirely irrelevant to all users.
{code}
2019-11-13 17:32:58,654 [shutdown-hook-0] DEBUG s3a.S3AFileSystem (S3AFileSystem.java:close(3126)) - Filesystem s3a://hwdev-steve-ireland-new is closed
2019-11-13 17:32:58,656 [shutdown-hook-0] INFO s3a.S3AFileSystem (HadoopExecutors.java:shutdown(118)) - Gracefully shutting down executor service. Waiting max 30 SECONDS
2019-11-13 17:32:58,656 [shutdown-hook-0] INFO s3a.S3AFileSystem (HadoopExecutors.java:shutdown(129)) - Succesfully shutdown executor service
2019-11-13 17:32:58,656 [shutdown-hook-0] INFO s3a.S3AFileSystem (HadoopExecutors.java:shutdown(118)) - Gracefully shutting down executor service. Waiting max 30 SECONDS
2019-11-13 17:32:58,656 [shutdown-hook-0] INFO s3a.S3AFileSystem (HadoopExecutors.java:shutdown(129)) - Succesfully shutdown executor service
{code}
We don't need to inflict this on anyone. Proposed: downgrade the logs to info. No need for tests
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org