You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Daniel Templeton (JIRA)" <ji...@apache.org> on 2016/12/08 00:23:58 UTC
[jira] [Commented] (YARN-4843) [Umbrella] Revisit YARN
ProtocolBuffer int32 usages that need to upgrade to int64
[ https://issues.apache.org/jira/browse/YARN-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730423#comment-15730423 ]
Daniel Templeton commented on YARN-4843:
----------------------------------------
Judging by the amount of effort that went into YARN-4844, I'm concerned that the remaining sub-JIRAs might not make it into alpha-2. Any updates, [~wangda]?
> [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
> Affects Versions: 3.0.0-alpha1
> Reporter: Wangda Tan
> Priority: Critical
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org