[
https://issues.apache.org/jira/browse/HDFS-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897930#comment-15897930
]
Andrew Wang commented on HDFS-11152:
------------------------------------
There is a possibility for invalid IDs if people use an old version of OIV
against a newer FSImage. Normally, this kind of change should also bump the NN
LayoutVersion to guard against this kind of error, but it doesn't hurt to have
additional checks here just in case. Also during the alpha process, we haven't
been bumping the LV when making metadata changes since it's still in alpha.
> Start erasure coding policy ID number from 1 instead of 0 to void potential
> unexpected errors
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-11152
> URL: https://issues.apache.org/jira/browse/HDFS-11152
> Project: Hadoop HDFS
> Issue Type: Task
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: SammiChen
> Assignee: SammiChen
> Priority: Blocker
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-11152-v1.patch, HDFS-11152-v2.patch,
> HDFS-11152-v3.patch
>
>
> This task will change erasure coding policy ID number starting from 1 instead
> of current 0, to avoid some potential unexpected errors in codes since 0 is
> default value for integer variables.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
