hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12763) Make it so there must be WALs for a server to be marked dead
Date Sat, 27 Dec 2014 21:14:14 GMT

     [ https://issues.apache.org/jira/browse/HBASE-12763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-12763:
       Resolution: Fixed
    Fix Version/s:     (was: 0.98.10)
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks [~apurtell]

Turns out 0.98 has this in essence:

237         FileStatus[] logFolders = FSUtils.listStatus(this.fs, logsDirPath, null);
238         // Get online servers after getting log folders to avoid log folder deletion of
239         // checked in region servers . see HBASE-5916
240         Set<ServerName> onlineServers = ((HMaster) master).getServerManager().getOnlineServers()
241             .keySet();
243         if (logFolders == null || logFolders.length == 0) {
244           LOG.debug("No log files to split, proceeding...");
245           return serverNames;
246         }

.. which means I need to dig in on the phenomeon I've seen in the past on 0.98 branch.

Meantime, I've applied this to branch-1 and master. Resolving.

> 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: 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