[
https://issues.apache.org/jira/browse/HADOOP-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037909#comment-13037909
]
Hudson commented on HADOOP-7318:
--------------------------------
Integrated in Hadoop-Common-trunk #697 (See
[https://builds.apache.org/hudson/job/Hadoop-Common-trunk/697/])
HADOOP-7318. MD5Hash factory should reset the digester it returns.
Contributed by Todd Lipcon
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1126287
Files :
* /hadoop/common/trunk/CHANGES.txt
* /hadoop/common/trunk/src/test/core/org/apache/hadoop/io/TestMD5Hash.java
* /hadoop/common/trunk/src/java/org/apache/hadoop/io/MD5Hash.java
> MD5Hash factory should reset the digester it returns
> ----------------------------------------------------
>
> Key: HADOOP-7318
> URL: https://issues.apache.org/jira/browse/HADOOP-7318
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: 0.22.0
>
> Attachments: hadoop-7318.txt, hadoop-7318.txt
>
>
> Currently the getDigest() method in MD5Hash does not reset the digester it
> returns. Since it's a thread-local, this means that a previous aborted usage
> of the same digester could leave some state around. For example, if the
> secondary namenode receives an IOException while transfering the image, and
> does another image transfer with the same thread, it will think it has
> received an invalid digest.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
