You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/09/13 16:27:21 UTC
[jira] [Updated] (YARN-5009) NMLeveldbStateStoreService database
can grow substantially leading to longer recovery times
[ https://issues.apache.org/jira/browse/YARN-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe updated YARN-5009:
-----------------------------
Attachment: YARN-5009-branch-2.6.002.patch
The merge conflicts for branch-2.6 were trivial context differences. Attaching the branch-2.6 patch for reference, and I will commit this to branch-2.6 later today.
> NMLeveldbStateStoreService database can grow substantially leading to longer recovery times
> -------------------------------------------------------------------------------------------
>
> Key: YARN-5009
> URL: https://issues.apache.org/jira/browse/YARN-5009
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Fix For: 2.7.3, 3.0.0-alpha1
>
> Attachments: YARN-5009-branch-2.6.002.patch, YARN-5009.001.patch, YARN-5009.002.patch
>
>
> Similar to the RM case in YARN-5008, I have seen state stores for nodemanagers with high container churn become significantly larger than they should be due to lack of sufficient database compaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org