hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wang XL (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13657) INodeId's LAST_RESERVED_ID may not as expected and the comment is misleading
Date Tue, 05 Jun 2018 13:50:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wang XL updated HDFS-13657:
---------------------------
    Attachment: HDFS-13657-trunk.001.patch
        Status: Patch Available  (was: Open)

> INodeId's LAST_RESERVED_ID may not as expected and the comment is misleading 
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-13657
>                 URL: https://issues.apache.org/jira/browse/HDFS-13657
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.1.0, 2.7.7
>            Reporter: Wang XL
>            Priority: Trivial
>         Attachments: HDFS-13657-trunk.001.patch
>
>
> The comment of class INodeId is misleading. In the comment, Id 1 to 1000 are reserved
for potential future usage, but code\{{public static final long LAST_RESERVED_ID = 2 <<
14 - 1}} will result 1 to 16384 are reserved. At the same time , operator '-' priority
is higher than '<<', \{{2 << 14 - 1}} is not equal to \{{(2 <<14) - 1}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message