[jira] [Comment Edited] (HBASE-14317) Stuck FSHLog: bad disk (HDFS-8960) and can't roll WAL

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-14317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721201#comment-14721201 ] 

stack edited comment on HBASE-14317 at 8/29/15 6:40 PM:
--------------------------------------------------------

You have HBASE-13971 [~eclark] ? You are on 1.2? It went in here:

{code}
Author: tedyu <yu...@gmail.com>
Date:   Thu Jul 16 16:45:24 2015 -0700

    HBASE-13971 Flushes stuck since 6 hours on a regionserver

commit 2862d68470c546de2a560e8ca2b96d080c50c234
{code}

It'd be interesting to know if it is in place on your rig. It may have fired but you are still stuck because root cause not addressed. If you do not have it, maybe it would have been enough. Thanks.


was (Author: stack):
You have HBASE-13971 [~eclark]

> Stuck FSHLog: bad disk (HDFS-8960) and can't roll WAL
> -----------------------------------------------------
>
>                 Key: HBASE-14317
>                 URL: https://issues.apache.org/jira/browse/HBASE-14317
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 1.1.1
>            Reporter: stack
>            Priority: Critical
>         Attachments: 14317.test.txt, HBASE-14317.patch, [Java] RS stuck on WAL sync to a dead DN - Pastebin.com.html, raw.php, subset.of.rs.log
>
>
> hbase-1.1.1 and hadoop-2.7.1
> We try to roll logs because can't append (See HDFS-8960) but we get stuck. See attached thread dump and associated log. What is interesting is that syncers are waiting to take syncs to run and at same time we want to flush so we are waiting on a safe point but there seems to be nothing in our ring buffer; did we go to roll log and not add safe point sync to clear out ringbuffer?
> Needs a bit of study. Try to reproduce.



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