[
https://issues.apache.org/jira/browse/DRILL-7542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019695#comment-17019695
]
Paul Rogers commented on DRILL-7542:
------------------------------------
[~arina], I can't recall this detail. I will speculate that I had to use the
same logging as the YARN framework. DoY has two executables: the client and the
App Master. Both make heavy use of the YARN and HDFS APIs. I may have found
that things worked best if I used the same logger for my code as YARN and HDFS
used.
That said, feel free to experiment; perhaps I missed something that would allow
us to get YARN and HDFS to log to our logger; I'm a pure novice at the logging
mechanisms.
> Fix Drill-on-Yarn logger
> ------------------------
>
> Key: DRILL-7542
> URL: https://issues.apache.org/jira/browse/DRILL-7542
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.16.0, 1.17.0
> Reporter: Arina Ielchiieva
> Priority: Major
>
> Drill project uses Logback logger backed by SLF4J:
> {noformat}
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> private static final Logger logger =
> LoggerFactory.getLogger(ResultsListener.class);
> {noformat}
> Drill-on-Yarn project uses commons loggin:
> {noformat}
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> private static final Log LOG = LogFactory.getLog(AbstractScheduler.class);
> {noformat}
> It would be nice if all project components used the same approach for logging.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
