[
https://issues.apache.org/jira/browse/YARN-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204654#comment-15204654
]
Karthik Kambatla commented on YARN-4843:
----------------------------------------
Sure, all client-facing updates need to be compatible. If we are doing it only
in trunk, we could at least do the updates between NM-RM incompatibly.
> [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)
