big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HDFS-16541. Fix a typo in NameNodeLayoutVersion (#4176)

Browse Source
This commit is contained in:
Happy-shi 2022-04-19 01:23:57 +08:00 committed by GitHub
parent 900682e712
commit f74f241636
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java
View File

@ -66,10 +66,10 @@ public static boolean supports(final LayoutFeature f, final int lv) {
* layout version is the earliest prior version to which a downgrade is * layout version is the earliest prior version to which a downgrade is
* possible after initiating rolling upgrade. If the feature cannot satisfy * possible after initiating rolling upgrade. If the feature cannot satisfy
* compatibility with any prior version, then set its minimum compatible * compatibility with any prior version, then set its minimum compatible
* lqyout version to itself to indicate that downgrade is impossible. * layout version to itself to indicate that downgrade is impossible.
* Satisfying compatibility might require adding logic to the new feature to * Satisfying compatibility might require adding logic to the new feature to
* reject operations or handle them differently while rolling upgrade is in * reject operations or handle them differently while rolling upgrade is in
* progress. In general, it's possible to satisfy compatiblity for downgrade * progress. In general, it's possible to satisfy compatibility for downgrade
* if the new feature just involves adding new edit log ops. Deeper * if the new feature just involves adding new edit log ops. Deeper
* structural changes, such as changing the way we place files in the metadata * structural changes, such as changing the way we place files in the metadata
* directories, might be incompatible. Feature implementations should strive * directories, might be incompatible. Feature implementations should strive
@ -98,7 +98,7 @@ public enum Feature implements LayoutFeature {
/** /**
* Feature that is added at layout version {@code lv} - 1. * Feature that is added at layout version {@code lv} - 1.
* @param lv new layout version with the addition of this feature * @param lv new layout version with the addition of this feature
* @param minCompatLV minimium compatible layout version * @param minCompatLV minimum compatible layout version
* @param description description of the feature * @param description description of the feature
*/ */
Feature(final int lv, int minCompatLV, final String description) { Feature(final int lv, int minCompatLV, final String description) {
@ -106,7 +106,7 @@ public enum Feature implements LayoutFeature {
} }
/** /**
* NameNode feature that is added at layout version {@code ancestoryLV}. * NameNode feature that is added at layout version {@code ancestorLV}.
* @param lv new layout version with the addition of this feature * @param lv new layout version with the addition of this feature
* @param ancestorLV layout version from which the new lv is derived from. * @param ancestorLV layout version from which the new lv is derived from.
* @param minCompatLV minimum compatible layout version * @param minCompatLV minimum compatible layout version