[
https://issues.apache.org/jira/browse/HDFS-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110124#comment-16110124
]
Hudson commented on HDFS-12107:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12099 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/12099/])
HDFS-12107. FsDatasetImpl#removeVolumes floods the logs when removing (wheat9:
rev 6814324c332a7d780f3b844fd6f1c62db2f6c88e)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/fsdataset/impl/FsDatasetImpl.java
> FsDatasetImpl#removeVolumes floods the logs when removing the volume
> --------------------------------------------------------------------
>
> Key: HDFS-12107
> URL: https://issues.apache.org/jira/browse/HDFS-12107
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha4
> Reporter: Haohui Mai
> Assignee: Kelvin Chu
> Fix For: 3.0.0-alpha4
>
> Attachments: HDFS-12107.001.patch
>
>
> FsDatasetImpl#removeVolumes() prints all block ids on a volume when removing
> it, which floods the log of DN.
> {noformat}
> for (String bpid : volumeMap.getBlockPoolList()) {
> List<ReplicaInfo> blocks = new ArrayList<>();
> for (Iterator<ReplicaInfo> it =
> volumeMap.replicas(bpid).iterator(); it.hasNext();) {
> ReplicaInfo block = it.next();
> final StorageLocation blockStorageLocation =
> block.getVolume().getStorageLocation();
> LOG.info("checking for block " + block.getBlockId() +
> " with storageLocation " + blockStorageLocation);
> if (blockStorageLocation.equals(sdLocation)) {
> blocks.add(block);
> it.remove();
> }
> }
> {noformat}
> The logging level should be {{DEBUG}} or {{TRACE}} instead of {{INFO}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
