You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 06:41:00 UTC

[jira] [Commented] (HDFS-15807) RefreshVolume fails when replacing DISK/ARCHIVE vol on same mount

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

Shilun Fan commented on HDFS-15807:
-----------------------------------

We are preparing to release hadoop 3.4.0 version, and I am doing some preparation work. The PR corresponding to this JIRA has been closed, so I changed the status of JIRA.

> RefreshVolume fails when replacing DISK/ARCHIVE vol on same mount
> -----------------------------------------------------------------
>
>                 Key: HDFS-15807
>                 URL: https://issues.apache.org/jira/browse/HDFS-15807
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode
>            Reporter: Leon Gao
>            Assignee: Leon Gao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When refreshing volumes to replace DISK/ARCHIVE on the same mount, it will fail because we have a check to see if the same vol type already exists on the mount.
> We can resolve it by removing volumes first, then add new volumes in refreshVolume logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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