[
https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327034#comment-14327034
]
Naganarasimha G R commented on YARN-3040:
-----------------------------------------
Thanks for briefing [~rkanter], and my queries or comments as follows :
bq. I think the Entities (YARN-3041) are mainly for writing/reading to/from the
ATS store. Most of the information stored in those Entities are not needed by
the user when submitting a job. All the user really needs to set is the IDs,
and some of these we can make optional or determine automatically (e.g. it's
obvious which cluster it's running on)
Yes i agree Flow, Cluster, Flow run not required for submitting a job and
hence if we are only passing the Entity ID's then tags should be sufficient
enough. But the concern what i had was based on the design doc <section 7, out
of scope, point 1> i am under the assumption that posting of Entities to ATSV2
can be done only by RM,NM and AM and client will not be able to post Flow, Flow
run and Cluster Entities explicitly. Hence wanted to know the approach for
clients to post Flow, Flow run and Cluster Entities. And wrt to Cluster info i
remember Vrushali mentioning about diff clusters like production and a test
cluster which they wanted to capture explicitly.
bq.100 characters per tag seems like it should be enough; if not, we can maybe
increase this limit? It is marked as @Evolving
If we are planning to pass Entity ID's to map the application hierarchy then i
feel 100 chars per tag should be sufficient. how about making it configurable
if required to store more information per tag
bq. For example, setFlowId(String id) would simply set the tag
yes i agree that these are not first class YARN concepts hence like you
mentioned YARN applications can take care of simplifying it. +1 for this
approach.
> [Data Model] Implement client-side API for handling flows
> ---------------------------------------------------------
>
> Key: YARN-3040
> URL: https://issues.apache.org/jira/browse/YARN-3040
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Robert Kanter
>
> Per design in YARN-2928, implement client-side API for handling *flows*.
> Frameworks should be able to define and pass in all attributes of flows and
> flow runs to YARN, and they should be passed into ATS writers.
> YARN tags were discussed as a way to handle this piece of information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
