[
https://issues.apache.org/jira/browse/SPARK-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190956#comment-14190956
]
Marcelo Vanzin commented on SPARK-1537:
---------------------------------------
bq. Please elaborate the changes in case I've missed some discussion
That's part of why I'm waiting on SPARK-1530. There's been no activity in a
while; I've been told there have been offline discussions but I don't see any
updates on the actual issue itself, so that's the main reason why I've been
holding off on this work: I don't feel it's a good investment of time to go
forward with something that might change in the near future.
It would be great if you could update that bug with a concrete plan for the
post-2.6 updates related to reliability and other features. If they really
don't affect the client API, then great, I can continue my Spark-side work
without worries. But again, I've mainly been waiting because of the radio
silence from the ATS side w.r.t. the issues that I think are important to Spark.
> Add integration with Yarn's Application Timeline Server
> -------------------------------------------------------
>
> Key: SPARK-1537
> URL: https://issues.apache.org/jira/browse/SPARK-1537
> Project: Spark
> Issue Type: New Feature
> Components: YARN
> Reporter: Marcelo Vanzin
> Assignee: Marcelo Vanzin
>
> It would be nice to have Spark integrate with Yarn's Application Timeline
> Server (see YARN-321, YARN-1530). This would allow users running Spark on
> Yarn to have a single place to go for all their history needs, and avoid
> having to manage a separate service (Spark's built-in server).
> At the moment, there's a working version of the ATS in the Hadoop 2.4 branch,
> although there is still some ongoing work. But the basics are there, and I
> wouldn't expect them to change (much) at this point.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
