[ https://issues.apache.org/jira/browse/YARN-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876762#comment-14876762 ]
Xianyin Xin commented on YARN-4190: ----------------------------------- Hi [~zxu], will we consider to fix the issue in YARN-4134 or YARN-3405, or just wait for the new preemption logic in YARN-2154? It blocks YARN-4090 and YARN-4120 which want to decouple scheduling and preemption and get a better performance. > missing container information in FairScheduler preemption log. > -------------------------------------------------------------- > > Key: YARN-4190 > URL: https://issues.apache.org/jira/browse/YARN-4190 > Project: Hadoop YARN > Issue Type: Improvement > Components: fairscheduler > Affects Versions: 2.7.1 > Reporter: zhihai xu > Assignee: zhihai xu > Priority: Trivial > > Add container information in FairScheduler preemption log to help debug. > Currently the following log doesn't have container information > {code} > LOG.info("Preempting container (prio=" + > container.getContainer().getPriority() + > "res=" + container.getContainer().getResource() + > ") from queue " + queue.getName()); > {code} > So it will be very difficult to debug preemption related issue for > FairScheduler. > Even the container information is printed in the following code > {code} > LOG.info("Killing container" + container + > " (after waiting for premption for " + > (getClock().getTime() - time) + "ms)"); > {code} > But we can't match these two logs based on the container ID. > It will be very useful to add container information in the first log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)