[
https://issues.apache.org/jira/browse/MAPREDUCE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093910#comment-17093910
]
Eric Payne edited comment on MAPREDUCE-7277 at 4/27/20, 8:30 PM:
-----------------------------------------------------------------
[~jeagles], we want this backported to 2.8, correct? I think patterns such as
the following won't build in 2.10 because LOG.debug(...) expects the second
parameter to be of type Throwable.
{code}
LOG.debug("IndexCache HIT: MapId {} found", mapId);
{code}
How would like to proceed?
was (Author: eepayne):
[~jeagles], we want this backported to 2.10, correct? I think patterns such as
the following won't build in 2.10 because LOG.debug(...) expects the second
parameter to be of type Throwable.
{code}
LOG.debug("IndexCache HIT: MapId {} found", mapId);
{code}
How would like to proceed?
> 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,
> MAPREDUCE-7277.002.patch, MAPREDUCE-7277.003.patch, MAPREDUCE-7277.004.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
