Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 815B3200B64 for ; Mon, 18 Jul 2016 22:11:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 80355160A5D; Mon, 18 Jul 2016 20:11:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C995D160A65 for ; Mon, 18 Jul 2016 22:11:21 +0200 (CEST) Received: (qmail 51074 invoked by uid 500); 18 Jul 2016 20:11:21 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 51047 invoked by uid 99); 18 Jul 2016 20:11:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2016 20:11:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AF89B2C0370 for ; Mon, 18 Jul 2016 20:11:20 +0000 (UTC) Date: Mon, 18 Jul 2016 20:11:20 +0000 (UTC) From: "Li Lu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3914) Entity created time should be part of the row key of entity table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 18 Jul 2016 20:11:22 -0000 [ https://issues.apache.org/jira/browse/YARN-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382970#comment-15382970 ] Li Lu commented on YARN-3914: ----------------------------- I'm checking through the JIRA list of YARN-5355 and saw this. Right now the schema of HBase tables are pretty much finalized, right? Personally I'd prefer the current way since it supports much easier query for (entityID, entityType). Also, determining the "start time" of a timeline entity is error pruning (something like YARN-5340, we spent quite a while to accurately locate the problem). My question here is, given the fact that this issue has been hanging for a year, shall we close it or work out some alternative solutions? > Entity created time should be part of the row key of entity table > ----------------------------------------------------------------- > > Key: YARN-3914 > URL: https://issues.apache.org/jira/browse/YARN-3914 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Zhijie Shen > Assignee: Zhijie Shen > Labels: YARN-5355 > > Entity created time should be part of the row key of entity table, between entity type and entity Id. The reason to have it is to index the entities. Though we cannot index the entities for all kinds of information, indexing them according to the created time is very necessary. Without it, every query for the latest entities that belong to an application and a type will scan through all the entities that belong to them. For example, if we want to list the 100 latest started containers in an YARN app. -- 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