[
https://issues.apache.org/jira/browse/HDFS-11306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822079#comment-15822079
]
Wei-Chiu Chuang commented on HDFS-11306:
----------------------------------------
[~yzhangal] thanks for the review. All failed tests looks flaky to me.
TestDFSRSDefault10x4StripedOutputStreamWithFailure,
TestDFSStripedOutputStreamWithFailure050,
TestDFSStripedOutputStreamWithFailure120 passed in my local tree.
TestDFSStripedOutputStreamWithFailure120 failed the first time, then passed the
second time.
> Print 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
> Attachments: HDFS-11306.001.patch, HDFS-11306.002.patch,
> HDFS-11306.003.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
