Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AF86A190FD for ; Thu, 28 Apr 2016 14:31:13 +0000 (UTC) Received: (qmail 75463 invoked by uid 500); 28 Apr 2016 14:31:13 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 75357 invoked by uid 500); 28 Apr 2016 14:31:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 75316 invoked by uid 99); 28 Apr 2016 14:31:12 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2016 14:31:12 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CCD1E2C1F54 for ; Thu, 28 Apr 2016 14:31:12 +0000 (UTC) Date: Thu, 28 Apr 2016 14:31:12 +0000 (UTC) From: "Jason Lowe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-5008) LeveldbRMStateStore database can grow substantially leading to long recovery times MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jason Lowe created YARN-5008: -------------------------------- Summary: LeveldbRMStateStore database can grow substantially leading to long recovery times Key: YARN-5008 URL: https://issues.apache.org/jira/browse/YARN-5008 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.7.0 Reporter: Jason Lowe Assignee: Jason Lowe On large clusters with high application churn the background compaction in leveldb may not be able to keep up with the write rate. This can lead to large leveldb databases that take many minutes to recover despite not having very much real data in the database to load. Most the time is spent traversing tables full of keys that have been deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)