hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12763) Make it so there must be WALs for a server to be marked dead
Date Sat, 03 Jan 2015 17:57:34 GMT

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

stack commented on HBASE-12763:

[~enis] It was committed mistakenly as part of the below.

  1 commit 2df74fbd4a85de1e5325ba6ad8595f2081238e29
  2 Author: stack <stack@apache.org>
  3 Date:   Sat Dec 27 09:41:44 2014 -0800
  5     HBASE-12746 [1.0.0RC0] Distributed Log Replay is on (HBASE-12577 was insufficient)
(Jeffrey Zhong)

I'll leave it as is unless you want me do different.  Let me go make a commet too over on

> Make it so there must be WALs for a server to be marked dead
> ------------------------------------------------------------
>                 Key: HBASE-12763
>                 URL: https://issues.apache.org/jira/browse/HBASE-12763
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>            Reporter: stack
>            Assignee: stack
>             Fix For: 1.0.0, 2.0.0, 1.1.0
>         Attachments: 12746-v2-master-and-098.patch
> The patch for this issue is a subset of the patch attached to the parent.  The parent
solves a 1.0.0-specific issue but part of the patch needs applying to 0.98 and to master to
fix an issue where Master on startup would think it was joining a cluster rather than undergoing
a fresh start just because it came across a directory named for a server that was once running
(the patch checks if the dir has WALs and if none, does not think the server a dead server).

This message was sent by Atlassian JIRA

View raw message