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

Hudson commented on HADOOP-8361:
--------------------------------

Integrated in Hadoop-Hdfs-trunk #1040 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1040/])
    HADOOP-8361. Avoid out-of-memory problems when deserializing strings. 
Contributed by Colin Patrick McCabe (Revision 1336945)

     Result = FAILURE
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1336945
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileStatus.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/permission/PermissionStatus.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/Text.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestText.java

                
> Avoid out-of-memory problems when deserializing strings
> -------------------------------------------------------
>
>                 Key: HADOOP-8361
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8361
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HADOOP-8361.001.patch, HADOOP-8361.002.patch, 
> HADOOP-8361.003.patch, HADOOP-8361.004.patch, HADOOP-8361.005.patch, 
> HADOOP-8361.006.patch, HADOOP-8361.007.patch
>
>
> In HDFS, we want to be able to read the edit log without crashing on an OOM 
> condition.  Unfortunately, we currently cannot do this, because there are no 
> limits on the length of certain data types we pull from the edit log.  We 
> often read strings without setting any upper limit on the length we're 
> prepared to accept.
> It's not that we don't have limits on strings-- for example, HDFS limits the 
> maximum path length to 8000 UCS-2 characters.  Linux limits the maximum user 
> name length to either 64 or 128 bytes, depending on what version you are 
> running.  It's just that we're not exposing these limits to the 
> deserialization functions that need to be aware of them.

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

        

Reply via email to