[
https://issues.apache.org/jira/browse/HDFS-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222805#comment-17222805
]
Brahma Reddy Battula edited comment on HDFS-15624 at 10/29/20, 10:07 AM:
-------------------------------------------------------------------------
{quote}, like the broken FsImage Compatibility, due to change in ordinal of
Storage Types. Rolling Upgrade issue.
{quote}
did you try it..? can you describe which scenario you tried and paste snapshot
before you talk about revert.?
was (Author: brahmareddy):
{quote}, like the broken FsImage Compatibility, due to change in ordinal of
Storage Types. Rolling Upgrade issue.
{quote}
did you try it..? can you describe which scenario you tried and paste snapshot
before you talk about revert.?
Based on the above
> 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
> 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
