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

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

                Author: ASF GitHub Bot
            Created on: 29/Oct/20 16:31
            Start Date: 29/Oct/20 16:31
    Worklog Time Spent: 10m 
      Work Description: vinayakumarb commented on pull request #2377:
URL: https://github.com/apache/hadoop/pull/2377#issuecomment-718871538


   > I think, you can hold on till HDFS-15660 addressed.
   
   I dont think need to hold this Jira, unless HDFS-15660 cant be solved in the 
same release as NVDIMM feature altogether.
   Once all comments of this jira are handled, can push this in. 
   HDFS-15660 will support handling of both PROVIDED and NVDIMM storage types 
for older clients in a generic way.
   
   So both can go independently but need to make sure both lands in same 
release.


----------------------------------------------------------------
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: 506269)
    Time Spent: 5h 20m  (was: 5h 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
>            Reporter: YaYun Wang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 5h 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