hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3508) avoid OOM while deserializing DelegationTokenIdentifer
Date Tue, 05 Jun 2012 21:09:23 GMT

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

Daryn Sharp commented on HDFS-3508:

I see.  I agree it would be a good idea to move the max length into {{AbstractDelegationTokenIdentifier}}
so {{Text}} isn't "polluted" with another's object notion of the max length of its fields.

Naming it something other than what it's defined to be would be nice.  Ie. something like
{{AbstractDelegationTokenIdentifier.USER_MAX_LEN}} instead of {{ONE_MEGABYTE}}.  If we were
to decide that 4KB was more than generous, it'd be goofy to rename the constant to {{FOUR_KILOBYTES}}.
> 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