[ 
https://issues.apache.org/jira/browse/HDFS-16427?focusedWorklogId=713620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-713620
 ]

ASF GitHub Bot logged work on HDFS-16427:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Jan/22 09:58
            Start Date: 24/Jan/22 09:58
    Worklog Time Spent: 10m 
      Work Description: tasanuma commented on pull request #3888:
URL: https://github.com/apache/hadoop/pull/3888#issuecomment-1019917288


   @tomscut Sorry for being late. I agree with adding more EC logs, but I feel 
that the log information is too detailed, and some variables duplicate with 
other variables. Could you please make it more concise and descriptive?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 713620)
    Time Spent: 40m  (was: 0.5h)

> Add debug log for BlockManager#chooseExcessRedundancyStriped
> ------------------------------------------------------------
>
>                 Key: HDFS-16427
>                 URL: https://issues.apache.org/jira/browse/HDFS-16427
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: tomscut
>            Assignee: tomscut
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> To solve this issueHDFS-16420 , we added some debug logs, which were also 
> necessary.  If there are other problems, we set the log level to DEBUG, which 
> is convenient to analyze it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to