You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2013/06/13 10:46:20 UTC

[jira] [Commented] (TAJO-51) Parallel Container Launch of TaskRunnerLauncherImpl

    [ https://issues.apache.org/jira/browse/TAJO-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682035#comment-13682035 ] 

Jihoon Son commented on TAJO-51:
--------------------------------

+1 
Great! 
Large overhead of container launch is a significant problem.
                
> Parallel Container Launch of TaskRunnerLauncherImpl
> ---------------------------------------------------
>
>                 Key: TAJO-51
>                 URL: https://issues.apache.org/jira/browse/TAJO-51
>             Project: Tajo
>          Issue Type: Improvement
>          Components: master
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>              Labels: yarn
>             Fix For: 0.2-incubating
>
>         Attachments: TAJO-51.patch
>
>
> TaskRunnerLauncherImpl plays a role to launch remote containers via the proxy of ContainerManager. This implementation sequentially launches containers, so it may take a long time in large clusters. For example, it consumes about 5 seconds for starting 128 containers in our cluster, consisting of 32 nodes. 
> To relieve this time-consuming work, we can make this part parallel by using ExecutorService.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira