Ok, no worries. I agree that this single AM model would be very close to a
mini-job tracker. One of the options we're investigating having 1 yarn Tez AM
running all our DAGs. Given this AM already has all the resources/containers,
we were thinking this could save on the cost of AM, and container
initialization.
We haven't looked into tez recovery as well. Durability is one of our big
concerns as well.
On Thursday, October 20, 2016 12:44 PM, Hitesh Shah <hit...@apache.org>
wrote:
Not supported as of now. There are multiple aspects to supporting this
properly. One of the most important issues to address would be to do proper QoS
across various DAGs i.e. what kind of policies would need to be built out to
run multiple DAGs to completion within a limited amount of resources. The model
would become close to a mini-jobtracker or a spark-standalone cluster.
Could you provide more details on what you are trying to achieve? We could try
and provide different viewpoints on trying to get you to a viable solution.
— Hitesh
> On Oct 20, 2016, at 10:52 AM, Madhusudan Ramanna <m.rama...@ymail.com> wrote:
>
> Hello Folks,
>
> http://hortonworks.com/blog/introducing-tez-sessions/
>
> From the above post it seems like DAGs can only be executed serially. Could
> DAGs be executed in parallel on one Tez AM ?
>
> thanks,
> Madhu
