You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2017/07/26 01:54:00 UTC

[jira] [Updated] (HBASE-18054) log when we add/remove failed servers in client

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

Andrew Purtell updated HBASE-18054:
-----------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 1.5.0
                   1.4.0
                   3.0.0
                   2.0.0
           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
>         Attachments: HBASE-18054.patch, HBASE-18054.v2.master.patch, HBASE-18054.v3.master.patch, HBASE-18054.v4.master.patch, HBASE-18054.v5.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
(v6.4.14#64029)