[
https://issues.apache.org/jira/browse/HDFS-14494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860179#comment-16860179
]
Hudson commented on HDFS-14494:
-------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16710 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16710/])
HDFS-14494. Move Server logging of StatedId inside (weichiu: rev
d6d95d2686bfc1d1e5511f60f169195734e2998e)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/GlobalStateIdContext.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Move Server logging of StatedId inside receiveRequestState()
> ------------------------------------------------------------
>
> Key: HDFS-14494
> URL: https://issues.apache.org/jira/browse/HDFS-14494
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Konstantin Shvachko
> Assignee: Shweta
> Priority: Major
> Labels: newbie++
> Fix For: 3.3.0
>
> Attachments: HDFS-14494.001.patch
>
>
> HDFS-14270 introduced logging of the client and server StateIds in trace
> level. Unfortunately one of the arguments
> {{alignmentContext.getLastSeenStateId()}} holds a lock on FSEdits, which is
> called even if trace logging level is disabled. I propose to move logging
> message inside {{GlobalStateIdContext.receiveRequestState()}} where
> {{clientStateId}} and {{serverStateId}} already calculated and can be easily
> printed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
