[
https://issues.apache.org/jira/browse/HADOOP-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646692#action_12646692
]
Pete Wyckoff commented on HADOOP-4635:
--------------------------------------
There is 1 memory leak in 0.18.2. For every file opened in write mode, it never
calls pthread_mutex_destroy for a mutex. This would probably be a few 10s of
bytes per file.
For 0.19 and 0.20, it also leaks per hdfsConnect which happens on file opens,
chmod, mvdir, ... That is leaking a char * of the username.
There's also a bug open for fuse-dfs leaking FileSystem handles, but that is a
single handle per unique user/group combination doing operations, and so should
be very small and not worrisome as it is O(#of users) and # of users is small.
I'm glad you opened this and we looked at it.
This is 0.18.2, right?
> 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.20.0
> Reporter: Marc-Olivier Fleury
>
> 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 heap.
> 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.
