[
https://issues.apache.org/jira/browse/HADOOP-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029867#comment-13029867
]
Hudson commented on HADOOP-7183:
--------------------------------
Integrated in Hadoop-Common-22-branch #44 (See
[https://builds.apache.org/hudson/job/Hadoop-Common-22-branch/44/])
HADOOP-7183. svn merge -c 1100056 from trunk
> WritableComparator.get should not cache comparator objects
> ----------------------------------------------------------
>
> Key: HADOOP-7183
> URL: https://issues.apache.org/jira/browse/HADOOP-7183
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.1, 0.22.0
>
> Attachments: HADOOP-7183.patch, HADOOP-7183.patch
>
>
> HADOOP-6881 modified WritableComparator.get such that the constructed
> WritableComparator gets saved back into the static map. This is fine for
> stateless comparators, but some comparators have per-instance state, and thus
> this becomes thread-unsafe and causes errors in the shuffle where multiple
> threads are doing comparisons. An example of a Comparator with per-instance
> state is WritableComparator itself.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
