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 3DB25176CD for ; Wed, 13 May 2015 19:58:00 +0000 (UTC) Received: (qmail 1995 invoked by uid 500); 13 May 2015 19:58:00 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 1946 invoked by uid 500); 13 May 2015 19:58:00 -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 1931 invoked by uid 99); 13 May 2015 19:58:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 May 2015 19:58:00 +0000 Date: Wed, 13 May 2015 19:58:00 +0000 (UTC) From: "Zhijie Shen (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3625) RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put 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-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542582#comment-14542582 ] Zhijie Shen commented on YARN-3625: ----------------------------------- bq. To handle this scenario, I relax the domain checking to mean if a domain is non-existent we can treat this as if we are in the temporary state we have staged the domain to be written for the related entity but have not yet written it to the database. I see. What to do with the following case if entity1 of domain1 relates to entity2 of domain2, and they're put in a same batch? According to the patch, it seems that the relation will be allowed, right? However, we previously stop the relationship across domains. > RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put > -------------------------------------------------------------------------- > > Key: YARN-3625 > URL: https://issues.apache.org/jira/browse/YARN-3625 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Jonathan Eagles > Assignee: Jonathan Eagles > Attachments: YARN-3625.1.patch, YARN-3625.2.patch > > > RollingLevelDBTimelineStore batches all entities in the same put to improve performance. This causes an error when relating to an entity in the same put however. -- This message was sent by Atlassian JIRA (v6.3.4#6332)