Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- duplicates
-
MAPREDUCE-6199 AbstractCounters are not reset completely on deserialization
- Resolved