hbase-issues mailing list archives

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

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

Todd Lipcon commented on HBASE-4275:
------------------------------------

I thought about adding a boolean or something there, but figured that, since this is just
keeping a log on the master, adn not a Map<Server, String>, it would be OK. Even if
there are multiple ABORTs for a given server, it's an improvement over what we have now, right?

We can later extend this to hook into log4j and perhaps propagate other ERROR level messages
in a nicely configurable (and throttled) way, but I think this feature is useful on its own.
Sound good?

> 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

        

Mime
View raw message