hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-7183) WritableComparator.get should not cache comparator objects
Date Fri, 11 Mar 2011 18:23:59 GMT
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
            Priority: Blocker
             Fix For: 0.22.0


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

Mime
View raw message