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 "Jing Zhao (JIRA)" <ji...@apache.org> on 2015/08/07 20:52:45 UTC
[jira] [Commented] (HDFS-8877) Allow bypassing some minor
exceptions while loading editlog
[ https://issues.apache.org/jira/browse/HDFS-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662259#comment-14662259 ]
Jing Zhao commented on HDFS-8877:
---------------------------------
Maybe a simple way as the first step can be: 1) to provide a new configuration property for users to specify the specific editlog ops that certain exceptions can be ignored (i.e., logging the exception instead of failing the edits loading), and 2), we change the editlog loading code and allow some specific exceptions to be ignored. E.g., when loading {{OP_CLOS}} or {{OP_REASSIGN_LEASE}}, instead of directly throwing IOException if the file is not under construction, we change the code so that this check can only lead to a warn level log if the configuration is set.
> Allow bypassing some minor exceptions while loading editlog
> -----------------------------------------------------------
>
> Key: HDFS-8877
> URL: https://issues.apache.org/jira/browse/HDFS-8877
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
>
> Usually when users hit editlog corruption like HDFS-7587, before upgrading to a new version with the bug fix, a customized jar has to be provided by developers first to bypass the exception while loading edits. The whole process is usually painful.
> If we can confirm the corruption/exception is a known issue and can be ignored after upgrading to the newer version, it may be helpful to have the capability for users/developers to specify certain types/numbers of exceptions that can be bypassed while loading edits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)