Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 9 Jan 2017 21:36:58 +0000 (UTC)
From: "Wei-Chiu Chuang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13033188.1483997780000.689693.1483997818759@Atlassian.JIRA>
In-Reply-To: <JIRA.13033188.1483997780000@Atlassian.JIRA>
References: <JIRA.13033188.1483997780000@Atlassian.JIRA> <JIRA.13033188.1483997780797@arcas>
Subject: [jira] [Created] (HDFS-11306) Dump remaining edit logs from buffer
 if edit log can't be rolled.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 09 Jan 2017 21:37:20 -0000

Wei-Chiu Chuang created HDFS-11306:
--------------------------------------

             Summary: Dump remaining edit logs from buffer if edit log can't be rolled.
                 Key: HDFS-11306
                 URL: https://issues.apache.org/jira/browse/HDFS-11306
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: ha, namenode
            Reporter: Wei-Chiu Chuang
            Assignee: Wei-Chiu Chuang


In HDFS-10943 [~yzhangal] reported that edit log can not be rolled due to unexpected edit logs lingering in the buffer.

Unable to root cause the bug, I propose that we dump the remaining edit logs in the buffer into namenode log, before crashing namenode. Use this new capability to find the ops that sneaks into the buffer unexpectedly, and hopefully catch the bug.

This effort is orthogonal, but related to HDFS-11292, which adds additional informational logs to help debug this issue.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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