[ https://issues.apache.org/jira/browse/HDFS-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hanisha Koneru updated HDFS-10713: ---------------------------------- Attachment: HDFS-10713.012.patch Thanks [~chris.douglas] for reviewing the patch. - I have optimized the do while block as per your suggestion. - The setTimeStampOfLastReadLockReport and setTimeStampOfLastWriteLockReport methods are no longer necessary. I have removed them. - The Thread.sleep’s at lines 311 and 370 in TestFSNamesystem were removed as they are not required. We are testing for write/read lock held for a short time and hence having 0 lock held time would also work here. > Throttle FsNameSystem lock warnings > ----------------------------------- > > Key: HDFS-10713 > URL: https://issues.apache.org/jira/browse/HDFS-10713 > Project: Hadoop HDFS > Issue Type: Bug > Components: logging, namenode > Reporter: Arpit Agarwal > Assignee: Hanisha Koneru > Attachments: HDFS-10713.000.patch, HDFS-10713.001.patch, > HDFS-10713.002.patch, HDFS-10713.003.patch, HDFS-10713.004.patch, > HDFS-10713.005.patch, HDFS-10713.006.patch, HDFS-10713.007.patch, > HDFS-10713.008.patch, HDFS-10713.009.patch, HDFS-10713.010.patch, > HDFS-10713.011.patch, HDFS-10713.012.patch > > > The NameNode logs a message if the FSNamesystem write lock is held by a > thread for over 1 second. These messages can be throttled to at one most one > per x minutes to avoid potentially filling up NN logs. We can also log the > number of suppressed notices since the last log message. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org