[
https://issues.apache.org/jira/browse/HDFS-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804354#comment-17804354
]
ASF GitHub Bot commented on HDFS-15815:
---------------------------------------
tomasbanet commented on PR #2882:
URL: https://github.com/apache/hadoop/pull/2882#issuecomment-1881386023
Just upgraded our cluster from 3.1.x to 3.3.x, and seeing this log line
printed hundreds of times per minute:
```
INFO org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy: Not
enough replicas was chosen. Reason:{NO_REQUIRED_STORAGE_TYPE=1}
```
We have a single rack topology, with replication factor of 3.
For now working around this issue by setting log level of
BlockPlacementPolicy to WARN in log4j.properties:
```
log4j.logger.org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy=WARN
```
> if required storageType are unavailable, log the failed reason during
> choosing Datanode
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-15815
> URL: https://issues.apache.org/jira/browse/HDFS-15815
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: block placement
> Reporter: Yang Yun
> Assignee: Yang Yun
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.3.1, 3.4.0, 3.2.3
>
> Attachments: HDFS-15815.001.patch, HDFS-15815.002.patch,
> HDFS-15815.003.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For better debug, if required storageType are unavailable, log the failed
> reason "NO_REQUIRED_STORAGE_TYPE" when choosing Datanode.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
