[
https://issues.apache.org/jira/browse/YARN-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344639#comment-15344639
]
Sangjin Lee commented on YARN-5281:
-----------------------------------
If we're open to the limitation of a single node setup, there could be more
options (levelDB, etc.).
In the future, we are definitely open to production-ready implementations that
can be alternatives to the HBase implementation. We tried to make the storage
as pluggable as possible, and probably we could do more to facilitate this down
the road.
As you mentioned, we could also consider having configurations that turn off
some features (aggregation or some type of queries) if they turn out to be too
challenging for certain implementations. But that would need to come with the
explicit acknowledgment that one would lose some functionalities by doing so.
For example, if flow run aggregation is turned off, users need to know what to
expect.
> 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]
