Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 22 Sep 2015 04:31:04 +0000 (UTC)
From: "Shiwei Guo (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12895329.1442896214000.35255.1442896264105@Atlassian.JIRA>
In-Reply-To: <JIRA.12895329.1442896214000@Atlassian.JIRA>
References: <JIRA.12895329.1442896214000@Atlassian.JIRA>
 <JIRA.12895329.1442896214348@arcas>
Subject: [jira] [Created] (YARN-4199) Minimize lock time in
 LeveldbTimelineStore.discardOldEntities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Shiwei Guo created YARN-4199:
--------------------------------

             Summary: Minimize lock time in LeveldbTimelineStore.discardOldEntities
                 Key: YARN-4199
                 URL: https://issues.apache.org/jira/browse/YARN-4199
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: timelineserver, yarn
            Reporter: Shiwei Guo


I current implementation, LeveldbTimelineStore.discardOldEntities holds a writeLock on deleteLock, which will block other put operation, which eventually block the execution of YARN jobs(e.g. TEZ). When there is lots of history jobs in timelinestore, the block time will be very long. In our observation, it block all the TEZ jobs for several hours or longer. 

The possible solutions are:
- Optimize leveldb configuration,  so a full scan won't take long time.
- Take a snapshot of leveldb, and scan the snapshot, so we only need to hold lock while getSnapshot. One question is that whether snapshot will take long time or not, cause I have no experience with leveldb.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)