hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4275) RS should communicate fatal "aborts" back to the master
Date Tue, 30 Aug 2011 18:05:20 GMT

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

Jean-Daniel Cryans commented on HBASE-4275:

Looks good.

One thing I'm wondering is what happens if abort is called multiple times RS-side (let's say
we get a big GC, then we abort with SessionExpired then again because some ZK call failed).
IIRC there's another jira about adding a isAborted to HRS which might be useful.

> RS should communicate fatal "aborts" back to the master
> -------------------------------------------------------
>                 Key: HBASE-4275
>                 URL: https://issues.apache.org/jira/browse/HBASE-4275
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>         Attachments: 0005-HBASE-4275.-Report-fatals-to-HMaster-v2.patch, 0005-HBASE-4275.-Report-fatals-to-HMaster.patch
> When a region server aborts, it should attempt to send an RPC to the master that contains
(a) the reason for aborting, and (b) the last several KB of log messages, if available. This
should help a lot in debugging.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message