hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18054) log when we add/remove failed servers in client
Date Fri, 02 Jun 2017 22:08:04 GMT

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

Ali commented on HBASE-18054:

[~apurtell] would it be enough to log the string version of the throwable that led to the
failed server? For example, if it was from an IOException, it would log something like "server
failed because of java.io.IOException" or would you recommend a more descriptive message in
which case the user can just input the string? another option could be to log the stack trace

> log when we add/remove failed servers in client
> -----------------------------------------------
>                 Key: HBASE-18054
>                 URL: https://issues.apache.org/jira/browse/HBASE-18054
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, Operability
>    Affects Versions: 1.3.0
>            Reporter: Sean Busbey
>            Assignee: Ali
>         Attachments: HBASE-18054.patch, HBASE-18054.v2.master.patch, HBASE-18054.v3.master.patch
> Currently we log if a server is in the failed server list when we go to connect to it,
but we don't log anything about when the server got into the list.
> This means we have to search the log for errors involving the same server name that (hopefully)
managed to get into the log within {{FAILED_SERVER_EXPIRY_KEY}} milliseconds earlier (default
2 seconds).

This message was sent by Atlassian JIRA

View raw message