[
https://issues.apache.org/jira/browse/MYRIAD-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437205#comment-16437205
]
Juan Pedro commented on MYRIAD-88:
----------------------------------
This issue is already corrected, the level of the log in the class mentioned to
debug has been changed.
I have made an analysis of the log and for me it is correct. The INFO level,
informs what Myriad is doing.
I propose to change the following logs from INFO to WARN:
- NMExecutorCommandLineGenerator: 146
- DisconnectedEventHandler: 34
- ExecutorLostEventHandler: 39
- SlaveLostEventHandler: 37
I think they are warnings of possible errors due to misconfiguration and
warnings of 'anomalous operation' in third-party systems. In this way the WARN
level is more concrete when there is something 'weird'.
Also from WARN to ERROR:
- Main: 294
> Reduce verbose logging
> ----------------------
>
> Key: MYRIAD-88
> URL: https://issues.apache.org/jira/browse/MYRIAD-88
> Project: Myriad
> Issue Type: Improvement
> Reporter: Santosh Marella
>
> One instance of "INFO" logging that should perhaps be at "DEBUG" level is
> 15/04/06 08:15:52 INFO handlers.ResourceOffersEventHandler: Received offers 2
> 15/04/06 08:15:52 INFO handlers.ResourceOffersEventHandler: No pending
> tasks, declining all offers
> 15/04/06 08:15:55 INFO handlers.ResourceOffersEventHandler: Received offers 2
> 15/04/06 08:15:55 INFO handlers.ResourceOffersEventHandler: No pending
> tasks, declining all offers
> 15/04/06 08:15:56 INFO handlers.ResourceOffersEventHandler: Received offers 1
> 15/04/06 08:15:56 INFO handlers.ResourceOffersEventHandler: No pending
> tasks, declining all offers
> There might be other instances where Myriad is logging too much.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
