hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiandan Yang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-12748) Standby NameNode memory leak when accessing webhdfs GETHOMEDIRECTORY
Date Tue, 31 Oct 2017 03:24:00 GMT
Jiandan Yang  created HDFS-12748:

             Summary: Standby NameNode memory leak when accessing webhdfs GETHOMEDIRECTORY
                 Key: HDFS-12748
                 URL: https://issues.apache.org/jira/browse/HDFS-12748
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs
    Affects Versions: 2.8.2
            Reporter: Jiandan Yang 

In our production environment, the standby NN often do fullgc, through mat we found the largest
object is FileSystem$Cache, which contains 7,844,890 DistributedFileSystem.
By view hierarchy of method FileSystem.get() , I found only NamenodeWebHdfsMethods#get call
FileSystem.get(). I don't know why creating different DistributedFileSystem every time instead
of get a FileSystem from cache.

      final String js = JsonUtil.toJsonString("Path",
          FileSystem.get(conf != null ? conf : new Configuration())
      return Response.ok(js).type(MediaType.APPLICATION_JSON).build();
When we close FileSystem when GETHOMEDIRECTORY, NN don't do fullgc.

      FileSystem fs = null;
      try {
        fs = FileSystem.get(conf != null ? conf : new Configuration());
        final String js = JsonUtil.toJsonString("Path",
        return Response.ok(js).type(MediaType.APPLICATION_JSON).build();
      } finally {
        if (fs != null) {

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message