Issue Details (XML | Word | Printable)

Key: HADOOP-4635
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Pete Wyckoff
Reporter: Marc-Olivier Fleury
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Hadoop Common

Memory leak ?

Created: 11/Nov/08 07:31 PM   Updated: 08/Jul/09 05:05 PM
Return to search
Component/s: None
Affects Version/s: 0.19.0, 0.20.0
Fix Version/s: 0.18.3, 0.19.1

Time Tracking:
Not Specified

File Attachments:
  Size
File Licensed for inclusion in ASF works HADOOP-4635.txt.0.18 2008-11-25 08:11 PM Pete Wyckoff 3 kB
File Licensed for inclusion in ASF works HADOOP-4635.txt.0.19 2008-11-25 08:12 PM Pete Wyckoff 2 kB
File patch-hadoop4635.test_18 2008-11-25 08:05 PM Pete Wyckoff 32 kB
File patch-hadoop4635.test_19 2008-11-25 08:06 PM Pete Wyckoff 61 kB
File TEST-TestFuseDFS.txt-4635 2008-11-25 08:11 PM Pete Wyckoff 36 kB
Issue Links:
Reference
 

Hadoop Flags: Reviewed
Release Note:
fix memory leak of user/group information in fuse-dfs

Resolution Date: 02/Dec/08 07:08 PM


 Description  « Hide
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



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.