Junping Du commented on YARN-2347:

bq. On the other side, timeline server is a stateless machine, but it will 
still use this version stack. StateVersion may make users consider it stateful. 
If StateVersion is going to be only used for the storage layer, something like 
StoreVersion sounds better to me.
That's good point. Can we think it is for application's state that stored in 
timeline store? If still no reasonable, let's get back to version. The problem 
of StoreVersion is: it sounds like a version for store implementation. For 
example, v1 for LevelDB, v2 for some others (HBase), etc. What do you think?
bq.  it may be better to add some more javadoc for StateVersion to let users 
know what it is really about.
Also good point. Will fix it soon.

> Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in 
> yarn-server-common
> ----------------------------------------------------------------------------------------
>                 Key: YARN-2347
>                 URL: https://issues.apache.org/jira/browse/YARN-2347
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: YARN-2347-v2.patch, YARN-2347-v3.patch, YARN-2347.patch
> We have similar things for version state for RM, NM, TS (TimelineServer), 
> etc. I think we should consolidate them into a common object.

This message was sent by Atlassian JIRA

Reply via email to