[
https://issues.apache.org/jira/browse/TEZ-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101894#comment-14101894
]
Jonathan Eagles edited comment on TEZ-1363 at 8/19/14 5:50 AM:
---------------------------------------------------------------
v2 patch uses the regular scheduler with a LocalContainerAllocator and has
added tests for local mode for both with and without container reuse. I'm still
tracking down a Futures exception. But am looking for feedback. [~sseth], any
thoughts on the patch design?
{quote}
SEVERE: RuntimeException while executing runnable
com.google.common.util.concurrent.Futures$6@28b53b32 with executor
java.util.concurrent.ThreadPoolExecutor@1241647f
{quote}
was (Author: jeagles):
v2 patch uses the regular scheduler with a LocalContainerAllocator and has
added tests for local mode for both with and without container reuse. I'm still
tracking down a Futures exception. But am looking for feedback. [~sseth], any
thoughts?
{quote}
SEVERE: RuntimeException while executing runnable
com.google.common.util.concurrent.Futures$6@28b53b32 with executor
java.util.concurrent.ThreadPoolExecutor@1241647f
{quote}
> Make use of the regular scheduler when running in LocalMode
> -----------------------------------------------------------
>
> Key: TEZ-1363
> URL: https://issues.apache.org/jira/browse/TEZ-1363
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Jonathan Eagles
> Attachments: TEZ-1363-v1.patch, TEZ-1363-v2.patch
>
>
> In TEZ-708, we decided to introduce a new scheduler for local mode - to keep
> things simple initially, and get local mode working.
> Eventually, however, scheduling should go through the regular task scheduler
> - which should be able to get containers from YARN / LocalAllocator / other
> sources - and treat them as a regular container for scheduling purposes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
