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

ASF GitHub Bot logged work on HDFS-15624:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Jan/21 07:55
            Start Date: 05/Jan/21 07:55
    Worklog Time Spent: 10m 
      Work Description: huangtianhua commented on pull request #2377:
URL: https://github.com/apache/hadoop/pull/2377#issuecomment-754470304


   @ayushtkn , in fact we don't have to hold this for HDFS-15660 as vinay said, 
the codes here is to fix the specific issues of NVDIMM, to avoid operations 
which related with storage type during rollingupgrade, to keep the orinal of 
storage type to make sure the editLog/fsimage works after restart namenode.  
IIUC, the miniCompatLV of namenodelayout version is introduced to make sure to 
refuse operations while rollingupgrade, so I think the approach is appropriate 
for the situation.


----------------------------------------------------------------
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: 531063)
    Time Spent: 8h 20m  (was: 8h 10m)

>  Fix the SetQuotaByStorageTypeOp problem after updating hadoop 
> ---------------------------------------------------------------
>
>                 Key: HDFS-15624
>                 URL: https://issues.apache.org/jira/browse/HDFS-15624
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 3.4.0
>            Reporter: YaYun Wang
>            Priority: Major
>              Labels: pull-request-available, release-blocker
>          Time Spent: 8h 20m
>  Remaining Estimate: 0h
>
> HDFS-15025 adds a new storage Type NVDIMM, changes the ordinal() of the enum 
> of StorageType. And, setting the quota by storageType depends on the 
> ordinal(), therefore, it may cause the setting of quota to be invalid after 
> upgrade.



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

Reply via email to