[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-2557.
--------------------------------
    Resolution: Duplicate

This should be resolved via MAPREDUCE-6199 (which adds in a reset API as well).

> Counters don't reset state when readFields() called
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-2557
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2557
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: William Slacum
>            Priority: Trivial
>         Attachments: MAPREDUCE-2557-style.patch, MAPREDUCE-2557-trunk.patch, 
> MAPREDUCE-2557.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> When calling readFields() on a Counters object, the internal state is not 
> completely reset. The IdentityHashMap<Enum<?>, Counter> cache retains all 
> previous mappings, even after the actual CounterGroups are changed. Using the 
> same Counters pointer over and over again results in the cache always keeping 
> the mapping for the first call to getCounter(Enum<?>). I've add a clear() 
> call to the cache when readFields() is called and added a unit test to verify 
> that it works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to