[
https://issues.apache.org/jira/browse/HBASE-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101308#comment-16101308
]
Hudson commented on HBASE-18054:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-2.0 #235 (See
[https://builds.apache.org/job/HBase-2.0/235/])
HBASE-18054 log when we add/remove failed servers in client (Ali) (apurtell:
rev e24f7f4675d5f4159f858985a3a3923673c04e4e)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/FailedServers.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestHBaseClient.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/NettyRpcConnection.java
* (add)
hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestFailedServersLog.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/BlockingRpcConnection.java
> 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)
