[ https://issues.apache.org/jira/browse/MAPREDUCE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089103#comment-17089103 ]
Jonathan Turner Eagles commented on MAPREDUCE-7277: --------------------------------------------------- Some very specific barriers and policies were put into place to ensure proper behavior. - totalMemoryUsed must be incremented before notifying waiting customers. - queue is now used as the ticket to enable the removal of an entry from the cache. - an item must finish construction in order to be removed from the cache so its size can be properly decremented. > IndexCache totalMemoryUsed differs from cache contents. > ------------------------------------------------------- > > Key: MAPREDUCE-7277 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7277 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Reporter: Jonathan Turner Eagles > Assignee: Jonathan Turner Eagles > Priority: Major > Attachments: IndexCacheActualSize.png, MAPREDUCE-7277.001.patch > > > It was observed recently in a nodemanager OOM that the memory was filled with > SpillRecords. However, the IndexCache was only 15% full (1.5MB used on a 10MB > configured cache size). In particular was noted that the booking variable > totalMemoryUsed, was out of sync with the contents of the cache showing 96% > full, thereby drastically reducing the effectiveness of the cache. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org