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 2018/04/06 16:32:00 UTC
[jira] [Commented] (HADOOP-15371) Wasb fs prints (jetty's) "Logging
initialized" message when instantiated
[ https://issues.apache.org/jira/browse/HADOOP-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428543#comment-16428543 ]
Steve Loughran commented on HADOOP-15371:
-----------------------------------------
{code}
[root@ctr-e138-1518143905142-192674-01-000005 ~]# hadoop fs -ls wasb://container@user.blob.core.windows.net
18/04/06 16:29:17 INFO util.log: Logging initialized @1428ms
18/04/06 16:29:17 ERROR azure.AzureNativeFileSystemStore: Service returned StorageException when checking existence of container container in account user.blob.core.windows.net
{code}
Happens because of the use of the eclipse Json utils, which create a log, which trigger jetty log init, ...
Fixes:
* edit log4j settings of hadoop itself to remove this message. What the adverse consequences be?
* set the JVM system property "org.eclipse.jetty.util.log.announce" to tell jetty not to print anything when initialized.
> Wasb fs prints (jetty's) "Logging initialized" message when instantiated
> ------------------------------------------------------------------------
>
> Key: HADOOP-15371
> URL: https://issues.apache.org/jira/browse/HADOOP-15371
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Priority: Minor
>
> Wasb initialization triggers an irrelevant log message from jetty about it being initialized.
--
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