hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-896) Roll up for long lived YARN
Date Mon, 15 Jul 2013 21:38:51 GMT

    [ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709021#comment-13709021

Enis Soztutar commented on YARN-896:

I think we also need generic provisioning service from YARN as well. We talked briefly about
this with Arun. From Hoya perspective, we would like to be able to use yarn to deploy multiple
different versions of HBase in the same cluster, with different configurations, and possibly
the hoya app master doing a rolling restart for updating running Hbase clusters. For this,
what we need are tarball and configuration distribution (instead of the regular rpm install).
Alternatively, we can also build this inside ambari provisioner, and wrap those API's in YARN,
so that ambari will deploy YARN, and YARN will use ambari services to deploy other bits. 
> Roll up for long lived YARN
> ---------------------------
>                 Key: YARN-896
>                 URL: https://issues.apache.org/jira/browse/YARN-896
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Robert Joseph Evans
> YARN is intended to be general purpose, but it is missing some features to be able to
truly support long lived applications and long lived containers.
> This ticket is intended to
>  # discuss what is needed to support long lived processes
>  # track the resulting JIRA.

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

View raw message