Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 24 Sep 2017 19:49:00 +0000 (UTC)
From: "Ajay Kumar (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13103753.1505945703000.188208.1506282540443@Atlassian.JIRA>
In-Reply-To: <JIRA.13103753.1505945703000@Atlassian.JIRA>
References: <JIRA.13103753.1505945703000@Atlassian.JIRA> <JIRA.13103753.1505945703057@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12516) Suppress the fsnamesystem lock
 warning on nn startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 24 Sep 2017 19:49:05 -0000


    [ https://issues.apache.org/jira/browse/HDFS-12516?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1617=
8339#comment-16178339 ]=20

Ajay Kumar commented on HDFS-12516:
-----------------------------------

[~anu], you are right. I think this is what [~arpitagarwal] suggested initi=
ally. Made the change in patch v3.

> Suppress the fsnamesystem lock warning on nn startup
> ----------------------------------------------------
>
>                 Key: HDFS-12516
>                 URL: https://issues.apache.org/jira/browse/HDFS-12516
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Ajay Kumar
>            Assignee: Ajay Kumar
>         Attachments: HDFS-12516.01.patch, HDFS-12516.02.patch, HDFS-12516=
.03.patch
>
>
> Whenever FsNameSystemLock is held for more than configured value of {{dfs=
.namenode.write-lock-reporting-threshold-ms}}, we log stacktrace and an ent=
ry in metrics. Loading FSImage from disk will usually cross this threshold.=
 We can suppress this FsNamesystem lock warning on NameNode startup.
> {code}
> 17/09/20 21:41:39 INFO namenode.FSNamesystem: FSNamesystem write lock hel=
d for 7159 ms via
> java.lang.Thread.getStackTrace(Thread.java:1552)
> org.apache.hadoop.util.StringUtils.getStackTrace(StringUtils.java:945)
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.writeUnlock(FSNamesys=
tem.java:1659)
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesys=
tem.java:1074)
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesy=
stem.java:703)
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.j=
ava:688)
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:=
752)
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:992)
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:976)
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.j=
ava:1701)
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1769)
> =E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82N=
umber of suppressed write-lock reports: 0
> =E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82L=
ongest write-lock held interval: 7159
> {code}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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