[
https://issues.apache.org/jira/browse/HDFS-16692?focusedWorklogId=795227&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-795227
]
ASF GitHub Bot logged work on HDFS-16692:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Jul/22 11:41
Start Date: 26/Jul/22 11:41
Worklog Time Spent: 10m
Work Description: ZanderXu opened a new pull request, #4630:
URL: https://github.com/apache/hadoop/pull/4630
### Description of PR
When we writing some ec data from client not in hdfs cluster, there are a
large number of INFO log output, as blew:
```
2022-07-26 15:50:40,973 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=17}
2022-07-26 15:50:40,974 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
2022-07-26 15:50:40,974 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=17}
2022-07-26 15:50:40,975 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
2022-07-26 15:50:40,975 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=17}
2022-07-26 15:50:40,976 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
2022-07-26 15:50:40,976 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
2022-07-26 15:50:40,977 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
2022-07-26 15:50:40,977 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=19}
2022-07-26 15:50:40,977 INFO blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas was
chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=3}
```
I feel that we should add detailed scope info in this log to show the scope
that we cannot select any good nodes from.
It will be convenient for us to quickly locate the scope in which the node
cannot be selected for what reason from the log.
Issue Time Tracking
-------------------
Worklog Id: (was: 795227)
Remaining Estimate: 0h
Time Spent: 10m
> Add detailed scope info in NotEnoughReplicas Reason logs.
> ---------------------------------------------------------
>
> Key: HDFS-16692
> URL: https://issues.apache.org/jira/browse/HDFS-16692
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: ZanderXu
> Assignee: ZanderXu
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we writing some ec data from client not in hdfs cluster, there are a
> large number of INFO log output, as blew:
> {code:shell}
> 2022-07-26 15:50:40,973 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=17}
> 2022-07-26 15:50:40,974 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
> 2022-07-26 15:50:40,974 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=17}
> 2022-07-26 15:50:40,975 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
> 2022-07-26 15:50:40,975 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=17}
> 2022-07-26 15:50:40,976 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
> 2022-07-26 15:50:40,976 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
> 2022-07-26 15:50:40,977 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=18}
> 2022-07-26 15:50:40,977 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=19}
> 2022-07-26 15:50:40,977 INFO blockmanagement.BlockPlacementPolicy
> (BlockPlacementPolicyDefault.java:chooseRandom(912)) - Not enough replicas
> was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1, TOO_MANY_NODES_ON_RACK=3}
> {code}
> I feel that we should add detailed scope info in this log to show the scope
> that we cannot select any good nodes from.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
