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 "Ke Han (Jira)" <ji...@apache.org> on 2023/06/27 01:49:00 UTC

[jira] [Commented] (HDFS-16984) Directory timestamp lost during the upgrade process

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

Ke Han commented on HDFS-16984:
-------------------------------

Hi [Ayush Saxena|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ayushtkn], I haven't found the root cause. But it should happen for all files that we uploaded.

The root cause could be related to how the timestamp is serialized to disk, and it's not deserialized properly in the new version.

> Directory timestamp lost during the upgrade process
> ---------------------------------------------------
>
>                 Key: HDFS-16984
>                 URL: https://issues.apache.org/jira/browse/HDFS-16984
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 2.10.2, 3.3.5
>            Reporter: Ke Han
>            Priority: Major
>         Attachments: GUBIkxOc.tar.gz
>
>
> h1. Symptoms
> The timestamp for a directory is lost after the upgrading from HDFS cluster 2.10.2 to 3.3.5.
> h1. Reproduce
> Start up a four-node HDFS cluster in 2.10.2 version.
> Execute the following commands. (The client is started up in NN, We have minimized the command sequence for reproducing)
> {code:java}
> bin/hdfs dfs -mkdir /GUBIkxOc
> bin/hdfs dfs -put -f -p -d /tmp/upfuzz/hdfs/GUBIkxOc/bQfxf /GUBIkxOc/
> bin/hdfs dfs -mkdir /GUBIkxOc/sKbTRjvS{code}
> Perform read in the old version
> {code:java}
> bin/hdfs dfs -ls     -t  -r -u /GUBIkxOc/
> Found 2 items
> drwxr-xr-x   - root  supergroup          0 1970-01-01 00:00 /GUBIkxOc/sKbTRjvS
> drwxr-xr-x   - 20001 998                 0 2023-04-17 16:15 /GUBIkxOc/bQfxf{code}
>  
> Then perform a full-stop upgrade to upgrade the entire cluster to 3.3.5. (Follow upgrade procedure in the website). When all nodes have started up, we perform the same read
> {code:java}
> Found 2 items
> drwxr-xr-x   - 20001 998                 0 1970-01-01 00:00 /GUBIkxOc/bQfxf
> drwxr-xr-x   - root  supergroup          0 1970-01-01 00:00 /GUBIkxOc/sKbTRjvS {code}
> The timestamp info of directory /GUBIkxOc/bQfxf is lost. It changes from 2023-04-17 16:15 to 1970-01-01 00:00.
>  
> I have also attached the required file: +/tmp/upfuzz/hdfs/GUBIkxOc/bQfxf+ . 



--
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