[jira] [Updated] (HDFS-13411) Should log more information when FSNameSystem is locked for a long time
[ https://issues.apache.org/jira/browse/HDFS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated HDFS-13411: --- Attachment: HDFS-13411.002.patch > Should log more information when FSNameSystem is locked for a long time > --- > > Key: HDFS-13411 > URL: https://issues.apache.org/jira/browse/HDFS-13411 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.8.2, 3.0.0 >Reporter: Tao Jie >Assignee: Tao Jie >Priority: Major > Attachments: HDFS-13411.001.patch, HDFS-13411.002.patch > > > Today when one RPC to namenode locks FSNameSystem for a long time, it would > print the stacktrace to the namenode log. However all we know from this log > is the operation name to the Namenode(such as create, delete). > It should print more information about the rpc call(like caller name, caller > ip, operation src), which blocks the namenode. So we can have a better tuning > to the HDFS. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13411) Should log more information when FSNameSystem is locked for a long time
[ https://issues.apache.org/jira/browse/HDFS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated HDFS-13411: --- Attachment: HDFS-13411.001.patch > Should log more information when FSNameSystem is locked for a long time > --- > > Key: HDFS-13411 > URL: https://issues.apache.org/jira/browse/HDFS-13411 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.8.2, 3.0.0 >Reporter: Tao Jie >Assignee: Tao Jie >Priority: Major > Attachments: HDFS-13411.001.patch > > > Today when one RPC to namenode locks FSNameSystem for a long time, it would > print the stacktrace to the namenode log. However all we know from this log > is the operation name to the Namenode(such as create, delete). > It should print more information about the rpc call(like caller name, caller > ip, operation src), which blocks the namenode. So we can have a better tuning > to the HDFS. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13411) Should log more information when FSNameSystem is locked for a long time
[ https://issues.apache.org/jira/browse/HDFS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated HDFS-13411: --- Status: Patch Available (was: Open) > Should log more information when FSNameSystem is locked for a long time > --- > > Key: HDFS-13411 > URL: https://issues.apache.org/jira/browse/HDFS-13411 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 3.0.0, 2.8.2 >Reporter: Tao Jie >Assignee: Tao Jie >Priority: Major > Attachments: HDFS-13411.001.patch > > > Today when one RPC to namenode locks FSNameSystem for a long time, it would > print the stacktrace to the namenode log. However all we know from this log > is the operation name to the Namenode(such as create, delete). > It should print more information about the rpc call(like caller name, caller > ip, operation src), which blocks the namenode. So we can have a better tuning > to the HDFS. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
