[
https://issues.apache.org/jira/browse/HDFS-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897120#comment-15897120
]
SammiChen edited comment on HDFS-11152 at 3/6/17 11:30 AM:
-----------------------------------------------------------
Hi [~jojochuang], thanks for review the patch! A new patch is available. I
gone through all EC policy related modules. It seems when user sets a EC
policy, only the policy name matters. The policy ID is just used internally to
save memory space. So an invalid policy only happens when the fsImage file is
tempered or editlog is tempered. Is there any known test utility routine which
can temper a fsimage or editlog, change a specific filed?
was (Author: sammi):
Hi [Wei-Chiu Chuang], thanks for review the patch! A new patch is available.
I gone through all EC policy related modules. It seems when user sets a EC
policy, only the policy name matters. The policy ID is just used internally to
save memory space.
> 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]
