[
https://issues.apache.org/jira/browse/HDFS-15624?focusedWorklogId=531046&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-531046
]
ASF GitHub Bot logged work on HDFS-15624:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jan/21 07:20
Start Date: 05/Jan/21 07:20
Worklog Time Spent: 10m
Work Description: ayushtkn commented on pull request #2377:
URL: https://github.com/apache/hadoop/pull/2377#issuecomment-754453252
@huangtianhua nopes you didn't. I know that is merged. That is what I said,
but there were assertions earlier on jira that we should hold this code in
Jira, for HDFS-15660. That would fix something or change our code here. So, we
held this jira because of that only. So, just want to wait, so that can be
clarified what needs to be done here post HDFS-15660.
And secondly the NamenodeLayout version approach had objection too as I
quoted above. We need to get an agreement over there.
For me the code is good enough, once we have clarifications regarding these
things, can conclude this
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 531046)
Time Spent: 8h 10m (was: 8h)
> 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 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]
