[
https://issues.apache.org/jira/browse/YARN-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343694#comment-15343694
]
Karthik Kambatla commented on YARN-5281:
----------------------------------------
Thanks for filing this, [~jrottinghuis]. Copying contents of my email here:
The reasons for my asking about alternate implementations: (1) ease of trying
it out for Yarn devs and iteration for bug fixes, improvements and (2) ease of
trying it for app-writers/users to figure out if they should use the ATS.
A test implementation would be enough for #1, and would partially address #2. A
more substantial implementation would be nice, but I guess we need to look at
the ROI to decide whether adding that is a good idea.
On completeness, I agree. Further, for some backend implementations, it is
possible that a particular aggregation/query might be possible but too
expensive to turn on. What are your thoughts on provisions for the admin to
turn off some queries/aggregations?
> Explore supporting a simpler back-end implementation for ATS v2
> ---------------------------------------------------------------
>
> Key: YARN-5281
> URL: https://issues.apache.org/jira/browse/YARN-5281
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Joep Rottinghuis
>
> During the merge discussion [~kasha] raised the question whether we would
> support simpler backend for users to try out, in addition to the HBase
> implementation.
> The understanding is that this would not be meant to scale, but it could
> simplify initial adoption and early usage.
> I'm filing this jira to gather the merits and challenges of such approach in
> one place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
