[
https://issues.apache.org/jira/browse/HDFS-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223033#comment-17223033
]
Vinayakumar B commented on HDFS-15624:
--------------------------------------
No need to hold this Jira and No need to revert HDFS-15025 as long as all of
them (including HDFS-15660) lands up before release of 3.4.0.
In any case, if not able to fix any of these by the release time (which I think
we still have some time), then we can think of revert.
Right now, PR is handling the backward compatibility related issues (due to
change in StorageType order) and inclusion of new Storage policy, by bumping
the LayoutVersion and adding check against NVDIMM releated operations to block
during upgrade.
HDFS-15660 will be handled soon enough to solve issues of both PROVIDED and
NVDIMM in a generic way. Right now also, 2.x clients will not be able to talk
3.x namenode via {{getContentSummary()}} or {{getQuotaUsage()}} on directories
with Quota on Storage Types.
> 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 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]
