While YARN-373 addresses a bit of a different problem the use case of reuse of existing resources could be looked at few different ways. As I understand YARN-373 talks about reusing resources from an old container to spun off a new one. Another way of looking at the problem is to actually reuse a container itself as long as you can communicate with it. I've been experimenting with it recently and while I am not sure if the approach is valid or solves your use case, take a look here https://github.com/olegz/yaya/wiki/CoreFeatures#java-based-long-running-and-interact-able-application-containers. At least you'll get some ideas of what could be done.
Cheers Oleg On Tue, Apr 8, 2014 at 10:53 AM, Krishna Kishore Bonagiri < [EMAIL PROTECTED]> wrote:
As Oleg mentioned, container-reuse is done at ApplicationMaster level currently. Tez's ApplicationMaster is one of them.
Thanks, - Tsuyoshi
On Thu, Apr 24, 2014 at 2:03 AM, Oleg Zhurakousky <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext