hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pete Wyckoff (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4635) Memory leak ?
Date Fri, 21 Nov 2008 21:47:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649812#action_12649812

Pete Wyckoff commented on HADOOP-4635:

interesting. I am using the latest version of the code but against 17.1 so i also have permissions

we should definitely plug the num_groups hole that you mentioned though. 

> Memory leak ?
> -------------
>                 Key: HADOOP-4635
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4635
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fuse-dfs
>    Affects Versions: 0.19.0, 0.20.0
>            Reporter: Marc-Olivier Fleury
>            Priority: Minor
> I am running a process that needs to crawl a tree structure containing ~10K images, copy
the images to the local disk, process these images, and copy them back to HDFS.
> My problem is the following : after about 10h of processing, the processes crash, complaining
about a std::bad_alloc exception (I use hadoop pipes to run existing software). When running
fuse_dfs in debug mode, I get an outOfMemoryError, telling that there is no more room in the
> While the process is running, using top or ps, I notice that fuse is using up an increasing
amount of memory, until some limit is reached. At that point , the memory used is oscillating.
I suppose that this is due to the use of the virtual memory.
> This leads me to the conclusion that there is some memory leak in fuse_dfs, since the
only other programs running are Hadoop and the existing software, both thoroughly tested in
the past.
> My problem is that my knowledge concerning memory leak tracking is rather limited, so
I will need some instructions to get more insight concerning this issue.
> Thank you

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message