hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4843) [Umbrella] Revisit YARN ProtocolBuffer int32 usages that need to upgrade to int64
Date Thu, 08 Dec 2016 01:09:59 GMT

    [ https://issues.apache.org/jira/browse/YARN-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730678#comment-15730678
] 

Wangda Tan commented on YARN-4843:
----------------------------------

This JIRA is more like a reminder, from my side, I didn't see MUST-to-fix issues so far. So
downgrading to major to unblock next 3.x release.

> [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


Mime
View raw message