HADOOP-12958. PhantomReference for filesystem statistics can trigger OOM. Contributed by Sangjin Lee

(cherry picked from commit 9a09200a1f)
This commit is contained in:
Jason Lowe 2016-03-25 22:56:49 +00:00
parent 1a194f8751
commit 25b476e93b
1 changed files with 4 additions and 4 deletions

View File

@ -20,7 +20,7 @@ package org.apache.hadoop.fs;
import java.io.Closeable;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.lang.ref.PhantomReference;
import java.lang.ref.WeakReference;
import java.lang.ref.ReferenceQueue;
import java.net.URI;
import java.net.URISyntaxException;
@ -3070,7 +3070,7 @@ public abstract class FileSystem extends Configured implements Closeable {
/**
* Set of all thread-local data areas. Protected by the Statistics lock.
* The references to the statistics data are kept using phantom references
* The references to the statistics data are kept using weak references
* to the associated threads. Proper clean-up is performed by the cleaner
* thread when the threads are garbage collected.
*/
@ -3123,11 +3123,11 @@ public abstract class FileSystem extends Configured implements Closeable {
}
/**
* A phantom reference to a thread that also includes the data associated
* A weak reference to a thread that also includes the data associated
* with that thread. On the thread being garbage collected, it is enqueued
* to the reference queue for clean-up.
*/
private class StatisticsDataReference extends PhantomReference<Thread> {
private class StatisticsDataReference extends WeakReference<Thread> {
private final StatisticsData data;
public StatisticsDataReference(StatisticsData data, Thread thread) {