hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1833) RefCountedDB printing of stacktrace should be moved to trace logging
Date Fri, 26 Jul 2019 22:29:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894172#comment-16894172

Eric Yang commented on HDDS-1833:

[~swagle] Sorry, I don't think that is true.  

>From [Java spec|https://docs.oracle.com/javase/specs/jls/se7/html/jls-15.html#jls-15.12.4]:

Example Evaluation Order During Method Invocation

As part of an instance method invocation (ยง15.12), there is an expression that denotes the
object to be invoked. This expression appears to be fully evaluated before any part of any
argument expression to the method invocation is evaluated.{quote}

ExceptionUtils.getStackTrace() is fully evaluated before trace method invocation.

> RefCountedDB printing of stacktrace should be moved to trace logging
> --------------------------------------------------------------------
>                 Key: HDDS-1833
>                 URL: https://issues.apache.org/jira/browse/HDDS-1833
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode
>    Affects Versions: 0.4.0
>            Reporter: Mukul Kumar Singh
>            Assignee: Siddharth Wagle
>            Priority: Major
>              Labels: newbie
>         Attachments: HDDS-1833.01.patch, HDDS-1833.02.patch, HDDS-1833.03.patch
> RefCountedDB logs the stackTrace for both increment and decrement, this pollutes the

This message was sent by Atlassian JIRA

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

View raw message