[
https://issues.apache.org/jira/browse/HDFS-15995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang resolved HDFS-15995.
------------------------------------
Fix Version/s: 3.4.0
Resolution: Done
> Rework HDFS-15624 Fix the SetQuotaByStorageTypeOp problem after updating
> hadoop
> -------------------------------------------------------------------------------
>
> Key: HDFS-15995
> URL: https://issues.apache.org/jira/browse/HDFS-15995
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.4.0
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Blocker
> Fix For: 3.4.0
>
>
> As discussed in the mailing list,
> {quote}
> In HDFS-15624 (fix the function of setting quota by storage type), A new
> layout version was added
> NVDIMM_SUPPORT(-66, -61, "Support NVDIMM storage type");
> This was added for 3.4.0 (trunk)
> However, there's another jira
> HDFS-15566 (NN restart fails after RollingUpgrade from 3.1.3/3.2.1 to 3.3.0)
> SNAPSHOT_MODIFICATION_TIME(-66, -61, "Support modification time for
> snapshot");
> where Brahma wanted to add a new layout version in branch-3.3 (3.3.1). The
> patch got stalled awhile ago and I'm trying to commit it in preparation of
> 3.3.1 release.
> However, both new layout versions conflict because they intend to use the new
> same version id. We can't release 3.3.1 without HDFS-15566 but we can't use
> layout id -66 because of HDFS-15624.
> I propose:
> revert HDFS-15624 (NVDIMM_SUPPORT),
> commit HDFS-15566 (SNAPSHOT_MODIFICATION_TIME)
> re-work on HDFS-15624 but with layout version id -67
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
