[
https://issues.apache.org/jira/browse/FLINK-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282577#comment-14282577
]
Till Rohrmann commented on FLINK-1372:
--------------------------------------
I don't think that it is good to directly use the logger of the companion
object in an actor scenario. First and most of all, you have synchronous
logging calls which in case of multiple actors which access the same logger
will block each other. Furthermore, you don't get the information which actor
actually made the call, since you only see the class name and the calling
thread. If you have multiple actors of the same class in one JVM, then it all
looks the same to you.
By using Akka's LoggingAdapter we get asynchronous logging with mapped
diagnostic context information such as the calling thread, the calling actor
and other information. Admittedly, the MDC information cannot be processed by
log4j but still we have the advantage of non-blocking logging. By the way, the
MDC support is the reason why I wanted to switch to Logback as the default
logging backend.
I try to fix the issue right now.
> TaskManager and JobManager do not log startup settings any more
> ---------------------------------------------------------------
>
> Key: FLINK-1372
> URL: https://issues.apache.org/jira/browse/FLINK-1372
> Project: Flink
> Issue Type: Bug
> Components: JobManager, TaskManager
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Assignee: Till Rohrmann
> Fix For: 0.9
>
>
> In prior versions, the jobmanager and taskmanager logged a lot of startup
> options:
> - Environment
> - ports
> - memory configuration
> - network configuration
> Currently, they log very little. We should add the logging back in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
