[
https://issues.apache.org/jira/browse/HDFS-15624?focusedWorklogId=530579&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-530579
]
ASF GitHub Bot logged work on HDFS-15624:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jan/21 09:46
Start Date: 04/Jan/21 09:46
Worklog Time Spent: 10m
Work Description: ayushtkn commented on pull request #2377:
URL: https://github.com/apache/hadoop/pull/2377#issuecomment-753872315
Thanx @huangtianhua for the work here, Sorry I couldn't revert back to your
emails & pings.
@brahmareddybattula has objections on the jira with the approach itself.
Quoting him from the jira
>I dn't think bumping the namelayout is best solution, need to check other
way. ( may be like checking the client version during the upgrade.)
There is no code change post HDFS-15660? It was asserted the generic
solution shall solve this problem or will change something
So, We might need changes here post HDFS-15660. should wait for him, unless
he is convinced.
----------------------------------------------------------------
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: 530579)
Time Spent: 7h 40m (was: 7.5h)
> 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: 7h 40m
> 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]
