[jira] [Commented] (HDFS-16009) HDFS tiered storage support

2021-05-09 Thread Leon Gao (Jira) 


[ 
https://issues.apache.org/jira/browse/HDFS-16009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341671#comment-17341671
 ] 

Leon Gao commented on HDFS-16009:
-

[~jianghuazhu] Absolutely, please let me know if you have any suggestions or 
questions.

> HDFS tiered storage support
> ---
>
> Key: HDFS-16009
> URL: https://issues.apache.org/jira/browse/HDFS-16009
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Reporter: JiangHua Zhu
>Priority: Major
>
> HDFS currently stores data blocks on different data nodes. These data nodes 
> are random within the scope of the network topology (local rack/different 
> racks/node group).
> When the NameNode allocates DataNodes to the Block, it is randomly selected, 
> that is, each DataNode is selected equally.
> We should make a hierarchical strategy. For example, DataNode1, DataNode2, 
> and DataNode3 are the same level, and DataNode4 and DataNode5 are the same 
> level. Because the hardware between DataNodes may be different, in this case, 
> it is necessary for us to do tiered storage, so that DataNodes with poor 
> hardware can store up to 50%, and 40% or even lower. This is conducive to 
> cluster maintenance and stability.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (HDFS-16018) Optimize the display of hdfs "count -e" or "count -t" command

2021-05-09 Thread Hongbing Wang (Jira) 
Hongbing Wang created HDFS-16018:


 Summary: Optimize the display of hdfs "count -e" or "count -t" 
command
 Key: HDFS-16018
 URL: https://issues.apache.org/jira/browse/HDFS-16018
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: dfsclient
Reporter: Hongbing Wang
Assignee: Hongbing Wang
 Attachments: fs_count_fixed.png, fs_count_origin.png

The display of `fs -count -e`or `fs -count -t` is not aligned.

*Current display:*

*!fs_count_origin.png|width=1184,height=156!*

*Fixed display:*

*!fs_count_fixed.png|width=1217,height=157!*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Issue Comment Deleted] (HDFS-16017) RBF: The getListing method should not overwrite the Listings returned by the NameNode

2021-05-09 Thread Ayush Saxena (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ayush Saxena updated HDFS-16017:

Comment: was deleted

(was: Nopes, We can't do that. The mount entry will get preference always, 
Because if we tend to read or access a directory the path will get resolved 
with respect to the mount table first, so the reason for overwriting is that we 
won't be able to access the directory overlapping with mount entry, that is why 
we overwrite it with the mount entry in listing as well. )

> RBF: The getListing method should not overwrite the Listings returned by the 
> NameNode
> -
>
> Key: HDFS-16017
> URL: https://issues.apache.org/jira/browse/HDFS-16017
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Affects Versions: 3.3.1
>Reporter: zhu
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Regarding the getListing method, when the directory returned by NameNode is a 
> mount point in MountTable, the list returned by Namenode shall prevail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Work logged] (HDFS-16017) RBF: The getListing method should not overwrite the Listings returned by the NameNode

2021-05-09 Thread ASF GitHub Bot (Jira) 


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

ASF GitHub Bot logged work on HDFS-16017:
-

Author: ASF GitHub Bot
Created on: 10/May/21 04:40
Start Date: 10/May/21 04:40
Worklog Time Spent: 10m 
  Work Description: zhuxiangyi opened a new pull request #2993:
URL: https://github.com/apache/hadoop/pull/2993


   
   


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 593826)
Remaining Estimate: 0h
Time Spent: 10m

> RBF: The getListing method should not overwrite the Listings returned by the 
> NameNode
> -
>
> Key: HDFS-16017
> URL: https://issues.apache.org/jira/browse/HDFS-16017
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Affects Versions: 3.3.1
>Reporter: zhu
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Regarding the getListing method, when the directory returned by NameNode is a 
> mount point in MountTable, the list returned by Namenode shall prevail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (HDFS-16017) RBF: The getListing method should not overwrite the Listings returned by the NameNode

2021-05-09 Thread ASF GitHub Bot (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDFS-16017:
--
Labels: pull-request-available  (was: )

> RBF: The getListing method should not overwrite the Listings returned by the 
> NameNode
> -
>
> Key: HDFS-16017
> URL: https://issues.apache.org/jira/browse/HDFS-16017
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Affects Versions: 3.3.1
>Reporter: zhu
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Regarding the getListing method, when the directory returned by NameNode is a 
> mount point in MountTable, the list returned by Namenode shall prevail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (HDFS-16017) RBF: The getListing method should not overwrite the Listings returned by the NameNode

2021-05-09 Thread Ayush Saxena (Jira) 


[ 
https://issues.apache.org/jira/browse/HDFS-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341657#comment-17341657
 ] 

Ayush Saxena commented on HDFS-16017:
-

Nopes, We can't do that. The mount entry will get preference always, Because if 
we tend to read or access a directory the path will get resolved with respect 
to the mount table first, so the reason for overwriting is that we won't be 
able to access the directory overlapping with mount entry, that is why we 
overwrite it with the mount entry in listing as well. 

> RBF: The getListing method should not overwrite the Listings returned by the 
> NameNode
> -
>
> Key: HDFS-16017
> URL: https://issues.apache.org/jira/browse/HDFS-16017
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Affects Versions: 3.3.1
>Reporter: zhu
>Priority: Major
>
> Regarding the getListing method, when the directory returned by NameNode is a 
> mount point in MountTable, the list returned by Namenode shall prevail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (HDFS-16014) Issue in checking native pmdk lib by 'hadoop checknative' command

2021-05-09 Thread Hadoop QA (Jira) 


[ 
https://issues.apache.org/jira/browse/HDFS-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341656#comment-17341656
 ] 

Hadoop QA commented on HDFS-16014:
--

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime ||  Logfile || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
37s{color} | {color:blue}{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} || ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green}  0m  
0s{color} | {color:green}{color} | {color:green} No case conflicting files 
found. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green}{color} | {color:green} The patch does not contain any 
@author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red}{color} | {color:red} The patch doesn't appear to 
include any new or modified tests. Please justify why no new tests are needed 
for this patch. Also please list what manual steps were performed to verify 
this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} || ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 19m 
46s{color} | {color:green}{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 20m 
38s{color} | {color:green}{color} | {color:green} trunk passed with JDK 
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 18m  
8s{color} | {color:green}{color} | {color:green} trunk passed with JDK Private 
Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 8s{color} | {color:green}{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green}  1m 
31s{color} | {color:green}{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
16m 21s{color} | {color:green}{color} | {color:green} branch has no errors when 
building and testing our client artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
5s{color} | {color:green}{color} | {color:green} trunk passed with JDK 
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
36s{color} | {color:green}{color} | {color:green} trunk passed with JDK Private 
Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 21m 
19s{color} | {color:blue}{color} | {color:blue} Both FindBugs and SpotBugs are 
enabled, using SpotBugs. {color} |
| {color:green}+1{color} | {color:green} spotbugs {color} | {color:green}  2m 
17s{color} | {color:green}{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} || ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
52s{color} | {color:green}{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 20m 
18s{color} | {color:green}{color} | {color:green} the patch passed with JDK 
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 {color} |
| {color:red}-1{color} | {color:red} cc {color} | {color:red} 20m 18s{color} | 
{color:red}https://ci-hadoop.apache.org/job/PreCommit-HDFS-Build/598/artifact/out/diff-compile-cc-root-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.txt{color}
 | {color:red} root-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 with JDK 
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 generated 26 new + 301 unchanged - 26 
fixed = 327 total (was 327) {color} |
| {color:green}+1{color} | {color:green} golang {color} | {color:green} 20m 
18s{color} | {color:green}{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 20m 
18s{color} | {color:green}{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 18m  
8s{color} | {color:green}{color} | {color:green} the patch passed with JDK 
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 {color} |
| {color:red}-1{color} | {color:red} cc {color} | {color:red} 18m  8s{color} | 
{color:red}https://ci-hadoop.apache.org/job/PreCommit-HDFS-Build/598/artifact/out/diff-compile-cc-root-jdkPrivateBuild-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10.txt{color}
 | {color:red} root-jdkPrivateBuild-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 with 
JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 generated 10 new + 317 
unchanged - 10 fixed = 327 total (was 327) {color} |
| {color:green}+1{color} | {color:green}

[jira] [Commented] (HDFS-15968) Improve the log for The DecayRpcScheduler

2021-05-09 Thread Bhavik Patel (Jira) 


[ 
https://issues.apache.org/jira/browse/HDFS-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341655#comment-17341655
 ] 

Bhavik Patel commented on HDFS-15968:
-

[~hexiaoqiao] can you please commit the changes if no more review comments.

> Improve the log for The DecayRpcScheduler 
> --
>
> Key: HDFS-15968
> URL: https://issues.apache.org/jira/browse/HDFS-15968
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Reporter: Bhavik Patel
>Assignee: Bhavik Patel
>Priority: Minor
> Attachments: HDFS-15968.001.patch
>
>
> Improve the log for The DecayRpcScheduler to make use of the SELF4j logger 
> factory



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (HDFS-16017) RBF: The getListing method should not overwrite the Listings returned by the NameNode

2021-05-09 Thread zhu (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zhu updated HDFS-16017:
---
Affects Version/s: 3.3.1

> RBF: The getListing method should not overwrite the Listings returned by the 
> NameNode
> -
>
> Key: HDFS-16017
> URL: https://issues.apache.org/jira/browse/HDFS-16017
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Affects Versions: 3.3.1
>Reporter: zhu
>Priority: Major
>
> Regarding the getListing method, when the directory returned by NameNode is a 
> mount point in MountTable, the list returned by Namenode shall prevail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (HDFS-16017) RBF: The getListing method should not overwrite the Listings returned by the NameNode

2021-05-09 Thread zhu (Jira) 
zhu created HDFS-16017:
--

 Summary: RBF: The getListing method should not overwrite the 
Listings returned by the NameNode
 Key: HDFS-16017
 URL: https://issues.apache.org/jira/browse/HDFS-16017
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: zhu


Regarding the getListing method, when the directory returned by NameNode is a 
mount point in MountTable, the list returned by Namenode shall prevail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Assigned] (HDFS-16016) BPServiceActor add a new thread to handle IBR

2021-05-09 Thread JiangHua Zhu (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

JiangHua Zhu reassigned HDFS-16016:
---

Assignee: (was: JiangHua Zhu)

> BPServiceActor add a new thread to handle IBR
> -
>
> Key: HDFS-16016
> URL: https://issues.apache.org/jira/browse/HDFS-16016
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Reporter: JiangHua Zhu
>Priority: Minor
>
> Now BPServiceActor#offerService() is doing many things, FBR, IBR, heartbeat. 
> We can handle IBR independently to improve the performance of heartbeat and 
> FBR.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (HDFS-16016) BPServiceActor add a new thread to handle IBR

2021-05-09 Thread JiangHua Zhu (Jira) 
JiangHua Zhu created HDFS-16016:
---

 Summary: BPServiceActor add a new thread to handle IBR
 Key: HDFS-16016
 URL: https://issues.apache.org/jira/browse/HDFS-16016
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: JiangHua Zhu


Now BPServiceActor#offerService() is doing many things, FBR, IBR, heartbeat. We 
can handle IBR independently to improve the performance of heartbeat and FBR.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Assigned] (HDFS-16016) BPServiceActor add a new thread to handle IBR

2021-05-09 Thread JiangHua Zhu (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

JiangHua Zhu reassigned HDFS-16016:
---

Assignee: JiangHua Zhu

> BPServiceActor add a new thread to handle IBR
> -
>
> Key: HDFS-16016
> URL: https://issues.apache.org/jira/browse/HDFS-16016
> Project: Hadoop HDFS
>  Issue Type: Improvement
>Reporter: JiangHua Zhu
>Assignee: JiangHua Zhu
>Priority: Minor
>
> Now BPServiceActor#offerService() is doing many things, FBR, IBR, heartbeat. 
> We can handle IBR independently to improve the performance of heartbeat and 
> FBR.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (HDFS-16014) Issue in checking native pmdk lib by 'hadoop checknative' command

2021-05-09 Thread Feilong He (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feilong He updated HDFS-16014:
--
Attachment: (was: HDFS-16014-01.patch)

> Issue in checking native pmdk lib by 'hadoop checknative' command
> -
>
> Key: HDFS-16014
> URL: https://issues.apache.org/jira/browse/HDFS-16014
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: native
>Affects Versions: 3.4.0
>Reporter: Feilong He
>Assignee: Feilong He
>Priority: Major
> Attachments: HDFS-16014-01.patch
>
>
> In HDFS-14818, we proposed a patch to support checking native pmdk lib. The 
> expected target is to display hint to user regarding pmdk lib loaded state. 
> Recently, it was found that pmdk lib was not successfully loaded actually but 
> the `hadoop checknative` command still tells user that it was. This issue can 
> be reproduced by moving libpmem.so* from specified installed path to other 
> place, or directly deleting these libs, after the project is built.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (HDFS-16014) Issue in checking native pmdk lib by 'hadoop checknative' command

2021-05-09 Thread Feilong He (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feilong He updated HDFS-16014:
--
Attachment: HDFS-16014-01.patch
Status: Patch Available  (was: In Progress)

> Issue in checking native pmdk lib by 'hadoop checknative' command
> -
>
> Key: HDFS-16014
> URL: https://issues.apache.org/jira/browse/HDFS-16014
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: native
>Affects Versions: 3.4.0
>Reporter: Feilong He
>Assignee: Feilong He
>Priority: Major
> Attachments: HDFS-16014-01.patch
>
>
> In HDFS-14818, we proposed a patch to support checking native pmdk lib. The 
> expected target is to display hint to user regarding pmdk lib loaded state. 
> Recently, it was found that pmdk lib was not successfully loaded actually but 
> the `hadoop checknative` command still tells user that it was. This issue can 
> be reproduced by moving libpmem.so* from specified installed path to other 
> place, or directly deleting these libs, after the project is built.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (HDFS-16003) ProcessReport print invalidatedBlocks should judge debug level at first

2021-05-09 Thread Xiaoqiao He (Jira) 


[ 
https://issues.apache.org/jira/browse/HDFS-16003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341511#comment-17341511
 ] 

Xiaoqiao He commented on HDFS-16003:


Thanks [~lei w] and [~ayushtkn]. Would you mind to fix checkstyle as Yetus 
reports above and submit another patch?

> ProcessReport print invalidatedBlocks should judge debug level at first
> ---
>
> Key: HDFS-16003
> URL: https://issues.apache.org/jira/browse/HDFS-16003
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namanode
>Affects Versions: 3.3.0
>Reporter: lei w
>Assignee: lei w
>Priority: Minor
> Attachments: HDFS-16003.patch
>
>
> In BlockManager#processReport( ) method, we will print invalidated blocks if 
> log level is debug。We always traverse this invalidatedBlocks list without 
> considering the log level。I suggest to give priority to the log level before 
> printing, which can save the time of traversal if log  level is info.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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