You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "yuyanlei (Jira)" <ji...@apache.org> on 2022/09/14 11:00:00 UTC

[jira] [Commented] (HDFS-14831) Downgrade Failed from 3.2.0 to 2.7 because of incompatible stringtable

    [ https://issues.apache.org/jira/browse/HDFS-14831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604019#comment-17604019 ] 

yuyanlei commented on HDFS-14831:
---------------------------------

After testing Hadoop2.7.2 rolling upgrade Hadoop3.3.4, I conducted the degradation test. I encountered a problem when degrading Namenode, and an error was reported .
Check Issuse and find HDFS-14831 similar to the problem I encountered
I merge the COMMIT(https://github.com/lucasaytt/hadoop/commit/8a41edb089fbdedc5e7d9a2aeec63d126afea49f) mentioned in https://issues.apache.org/jira/browse/HDFS-14831 in Hadoop2.7.2
However, in the degraded Namenode (2.7.2), write operations cannot be performed and an error is reported  
The Owner and Group of the directory are displayed as Empty on the Web page
Subsequent discovery: GROUP and USER in PermissionStatusFormat in 2.7.2 are 25 and 23, respectively, while those in 3.3.4 are 24 and 24 .
I changed GROUP and USER to 24 and 24 in 2.7.2, which can be degraded successfully
This commit:https://github.com/lucasaytt/hadoop/commit/8a41edb089fbdedc5e7d9a2aeec63d126afea49f,Can it be merged into Hadoop2.7.2?   Is there any hidden danger?

 

> Downgrade Failed from 3.2.0 to 2.7 because of incompatible stringtable 
> -----------------------------------------------------------------------
>
>                 Key: HDFS-14831
>                 URL: https://issues.apache.org/jira/browse/HDFS-14831
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.2.0, 3.3.0, 3.1.3
>            Reporter: Hui Fei
>            Assignee: Hui Fei
>            Priority: Major
>
> Mentioned on HDFS-13596
> Incompatible StringTable changes cause downgrade from 3.2.0 to 2.7.2 failed
> commit message as follow, but issue not found
> {quote}
> commit 8a41edb089fbdedc5e7d9a2aeec63d126afea49f
> Author: Vinayakumar B <vi...@apache.org>
> Date:   Mon Oct 15 15:48:26 2018 +0530
>     Fix potential FSImage corruption. Contributed by Daryn Sharp.
> {quote} 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org