hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10713) Throttle FsNameSystem lock warnings
Date Fri, 02 Sep 2016 22:29:20 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459759#comment-15459759
] 

Mingliang Liu commented on HDFS-10713:
--------------------------------------

{quote}
If we just capture the longest lock held interval but lose the stack trace could that be an
acceptable solution. Mingliang Liu, what do you think?
{quote}

That makes sense in order to avoid overhead of too frequent capturing the stack trace. If
we find in the future we need the longest lock holding stack trace heavily, we can add it
back. Before that, operators can reduce the config {{dfs.lock.suppress.warning.interval.ms}}
for finer-granularity information. Thanks.

> 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message