You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Wei-Chiu Chuang (JIRA)" <ji...@apache.org> on 2019/06/10 17:25:00 UTC
[jira] [Updated] (HDFS-14494) Move Server logging of StatedId
inside receiveRequestState()
[ https://issues.apache.org/jira/browse/HDFS-14494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang updated HDFS-14494:
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.3.0
Status: Resolved (was: Patch Available)
Pushed to trunk.
Thanks [~shwetayakkali] for the patch and thanks [~shv] for reporting the issue!
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org