hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3508) avoid OOM while deserializing DelegationTokenIdentifer
Date Tue, 05 Jun 2012 19:13:24 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289648#comment-13289648

Colin Patrick McCabe commented on HDFS-3508:

Hi Daryn,

This was discussed in HADOOP-8361 and HDFS-3134.  Basically, having Text.ONE_MEGABYTE rather
than simply baking the constant into a method in class Text makes it clear what is going on
to people who do not carefully inspect all the methods of class Text.  Actually, this point
was first brought up by tlipcon-- my original change looked a lot like what you suggest--
hardcoding 1 MB into class Text itself.

I guess it would make sense to move the maximum length constant into AbstractDelegationTokenIdentifier.
> avoid OOM while deserializing DelegationTokenIdentifer
> ------------------------------------------------------
>                 Key: HDFS-3508
>                 URL: https://issues.apache.org/jira/browse/HDFS-3508
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.0.1-alpha
>         Attachments: HDFS-3508.001.patch
> avoid OOM while deserializing DelegationTokenIdentifer

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message