[ https://issues.apache.org/jira/browse/HADOOP-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867604#comment-15867604 ]
Wei-Chiu Chuang commented on HADOOP-13665: ------------------------------------------ I think the key here is to make the order of fallback codecs configurable, like in the case of security crypto codec. There are two benefits: (1) we might be able to support more codecs in the future (2) if one of the preferred codec is buggy, we could replace it without writing new code. This comes handy when troubleshotting a cluster, especially since this feature has not been verified in production (at least for us). > Erasure Coding codec should support fallback coder > -------------------------------------------------- > > Key: HADOOP-13665 > URL: https://issues.apache.org/jira/browse/HADOOP-13665 > Project: Hadoop Common > Issue Type: Sub-task > Components: io > Reporter: Wei-Chiu Chuang > Assignee: Kai Sasaki > Priority: Blocker > Labels: hdfs-ec-3.0-must-do > Attachments: HADOOP-13665.01.patch, HADOOP-13665.02.patch, > HADOOP-13665.03.patch, HADOOP-13665.04.patch > > > The current EC codec supports a single coder only (by default pure Java > implementation). If the native coder is specified but is unavailable, it > should fallback to pure Java implementation. > One possible solution is to follow the convention of existing Hadoop native > codec, such as transport encryption (see {{CryptoCodec.java}}). It supports > fallback by specifying two or multiple coders as the value of property, and > loads coders in order. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org