[
https://issues.apache.org/jira/browse/YARN-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234844#comment-14234844
]
Li Lu commented on YARN-2837:
-----------------------------
{quote}
Logic in Version loadedVersion = loadVersion(); Consider this scenario:
CURRENT_VERSION_INFO = 2.0; there’s no version info currently saved in
store-store. loadVersion returns 1.0; It’ll throw inCompatible exception, even
though it should not.
{quote}
This looks to be a valid concern, but I noticed similar logic also exist in
LeveldbTimelineStore. We need to be consistent on this logic.
{quote}
default path for state store is the same as time-line store for application
data. If apps posts massive data in store, will that also affect system data
seek performance ?
{quote}
The two leveldb stores are working on different leveldb files, so I think it's
fine.
> Timeline server needs to recover the timeline DT when restarting
> ----------------------------------------------------------------
>
> Key: YARN-2837
> URL: https://issues.apache.org/jira/browse/YARN-2837
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: YARN-2837.1.patch, YARN-2837.2.patch, YARN-2837.3.patch
>
>
> Timeline server needs to recover the stateful information when restarting as
> RM/NM/JHS does now. So far the stateful information only includes the
> timeline DT. Without recovery, the timeline DT of the existing YARN apps is
> not long valid, and cannot be renewed any more after the timeline server is
> restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
