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 83D0D189A6 for ; Fri, 13 Nov 2015 00:02:11 +0000 (UTC) Received: (qmail 64591 invoked by uid 500); 13 Nov 2015 00:02:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 64524 invoked by uid 500); 13 Nov 2015 00:02:11 -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 64493 invoked by uid 99); 13 Nov 2015 00:02:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Nov 2015 00:02:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 128EF2C1F5C for ; Fri, 13 Nov 2015 00:02:11 +0000 (UTC) Date: Fri, 13 Nov 2015 00:02:11 +0000 (UTC) From: "Li Lu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4265: ------------------------ Attachment: YARN-4265.YARN-4234.001.patch I refactored my code and added some unit tests. The current patch only depends on YARN-4234. I addressed comments raised by [~jlowe] in the previous round of review, with two pending actions that I think we can address in separate JIRAs: # Build a "fall-back" plugin to have the same behavior of YARN-3942. # Make caching storage pluggable. For the second item, right now my patch does _not_ depend on YARN-4219. So I'm setting the v1.5 plugin storage to use the memory storage system as the "caching" storage, similar to YARN-3942. I'm adding the v1.5 plugin storage (EntityGroupFSTimelineStore) in a module called hadoop-yarn-server-timeline-pluginstorage. This is slightly different to YARN-3942. We need a separate module because the new v1.5 storage depends on yarn-client, but we don't want ats server depends on yarn-client (The v1.5 storage is not a purely server side storage.). I'm naming it as "pluginstorage" because I'm considering to put the leveldb caching storage into this extension as well. > Provide new timeline plugin storage to support fine-grained entity caching > -------------------------------------------------------------------------- > > Key: YARN-4265 > URL: https://issues.apache.org/jira/browse/YARN-4265 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Li Lu > Assignee: Li Lu > Attachments: YARN-4265-trunk.poc_001.patch, YARN-4265.YARN-4234.001.patch > > > To support the newly proposed APIs in YARN-4234, we need to create a new plugin timeline store. The store may have similar behavior as the EntityFileTimelineStore proposed in YARN-3942, but cache date in cache id granularity, instead of application id granularity. Let's have this storage as a standalone one, instead of updating EntityFileTimelineStore, to keep the existing store (EntityFileTimelineStore) stable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)