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 35CA219FAB for ; Mon, 21 Mar 2016 17:06:26 +0000 (UTC) Received: (qmail 85463 invoked by uid 500); 21 Mar 2016 17:06:25 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 85361 invoked by uid 500); 21 Mar 2016 17:06:25 -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 85318 invoked by uid 99); 21 Mar 2016 17:06:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Mar 2016 17:06:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7106F2C1F5A for ; Mon, 21 Mar 2016 17:06:25 +0000 (UTC) Date: Mon, 21 Mar 2016 17:06:25 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4843) [Umbrella] Revisit YARN ProtocolBuffer int32 usages that need to upgrade to int64 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-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204621#comment-15204621 ] Wangda Tan commented on YARN-4843: ---------------------------------- [~kasha], actually we can do this in compatible way like what [~djp] suggested: add two int64 fields, deprecate int32 fields. User can set/get both fields, but int64 fields will be preferred. I would suggest to keep compatibility even we ship 3.0.0, all YARN applications use the Resource object frequently, it gonna be hard to ask everyone update lots of source code to use 3.0.0. > [Umbrella] Revisit YARN ProtocolBuffer int32 usages that need to upgrade to int64 > --------------------------------------------------------------------------------- > > Key: YARN-4843 > URL: https://issues.apache.org/jira/browse/YARN-4843 > Project: Hadoop YARN > Issue Type: Bug > Components: api > Reporter: Wangda Tan > > This JIRA is to track all int32 usages in YARN's ProtocolBuffer APIs that we possibly need to update to int64. > One example is resource API. We use int32 for memory now, if a cluster has 10k nodes, each node has 210G memory, we will get a negative total cluster memory. > We may have other fields may need to upgrade from int32 to int64. -- This message was sent by Atlassian JIRA (v6.3.4#6332)