[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16131072#comment-16131072 ] Hudson commented on HBASE-18054: FAILURE: Integrated in Jenkins build HBASE-14070.HLC #233 (See [https://builds.apache.org/job/HBASE-14070.HLC/233/]) HBASE-18054 log when we add/remove failed servers in client (Ali) (apurtell: rev 2fd8e824d584a6c898414c11e26cc3a0a83e7653) * (add) hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestFailedServersLog.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/NettyRpcConnection.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/BlockingRpcConnection.java * (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 > 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16101338#comment-16101338 ] Hudson commented on HBASE-18054: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3436 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3436/]) HBASE-18054 log when we add/remove failed servers in client (Ali) (apurtell: rev 2fd8e824d584a6c898414c11e26cc3a0a83e7653) * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestHBaseClient.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/FailedServers.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/NettyRpcConnection.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/BlockingRpcConnection.java * (add) hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestFailedServersLog.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)
[jira] [Commented] (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: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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16101172#comment-16101172 ] Hudson commented on HBASE-18054: FAILURE: Integrated in Jenkins build HBase-1.4 #819 (See [https://builds.apache.org/job/HBase-1.4/819/]) HBASE-18054 log when we add/remove failed servers in client (Ali) (apurtell: rev a4e1af1fcc5fc4280a044f1b6d1e0d9636e8ee0d) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/FailedServers.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/BlockingRpcConnection.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 > 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16100862#comment-16100862 ] Andrew Purtell commented on HBASE-18054: Committing shortly, thanks! > 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, 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16100851#comment-16100851 ] Mike Drob commented on HBASE-18054: --- +1 v5 LGTM. > 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, 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16100784#comment-16100784 ] Andrew Purtell commented on HBASE-18054: Any more comments or concerns [~mdrob] ? > 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, 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16065683#comment-16065683 ] Hadoop QA commented on HBASE-18054: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 10s{color} | {color:blue} Docker mode activated. {color} | | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s{color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 2 new or modified test files. {color} | | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 12s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 0s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 45s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 21s{color} | {color:green} master passed {color} | | {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 50s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings. {color} | | {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m 44s{color} | {color:red} hbase-server in master has 10 extant Findbugs warnings. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s{color} | {color:green} master passed {color} | | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 13s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 57s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 50s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 50s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 41s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 23s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 27m 23s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m 27s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 43s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 20s{color} | {color:green} hbase-client in the patch passed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green}114m 46s{color} | {color:green} hbase-server in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 25s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}162m 14s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 | | JIRA Issue | HBASE-18054 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12874749/HBASE-18054.v5.master.patch | | Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck hbaseanti checkstyle compile | | uname | Linux 09903b4b969d 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / 8da6f06 | | Default Java | 1.8.0_131 | | findbugs | v3.1.0-RC1 | | findbugs | https://builds.apache.org/job/PreCommit-HBASE-Build/7365/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html | | findbugs | https://b
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16065473#comment-16065473 ] Ali commented on HBASE-18054: - thank you [~mdrob] for your feedback. i have made the changes in v5 patch > 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, 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16060014#comment-16060014 ] Mike Drob commented on HBASE-18054: --- {code} + private static Log LOG = LogFactory.getLog(FailedServers.class); {code} Nit: should be declared final. {code} - public synchronized void addToFailedServers(InetSocketAddress address) { + public synchronized void addToFailedServers(InetSocketAddress address, Throwable throwable) { {code} Should we have multiple methods instead to allow a gradual migration? I guess it's {{@IA.Private}}, so maybe it doesn't matter. {code} +assertEquals(nullException.toString(), "java.lang.NullPointerException"); +assertEquals(loggingEvent.getRenderedMessage(), "Added failed server with address " ++ addr.toString() + " to list caused by " + nullException.toString()); +assertNotEquals(loggingEvent.getRenderedMessage(), "Added failed server with address " ++ addr.toString() + " to list caused by " + iOException.toString()); {code} I don't think we need to verify the behaviour of NPE.toString. And I don't think we need to check that the message is both equal to and not equal to things. The equality check strongly implies the non-equality check. Nit: Argument order for JUnit is (expected, actual), you have it reversed. I really like the use of Mock here, I'm going to have to keep that in mind for when I'm doing something similar in the future. > 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, HBASE-18054.v4.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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16049932#comment-16049932 ] Hadoop QA commented on HBASE-18054: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 17s {color} | {color:blue} Docker mode activated. {color} | | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s {color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s {color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s {color} | {color:green} The patch appears to include 2 new or modified test files. {color} | | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 26s {color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 29s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 12s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m 10s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 31s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m 27s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 0s {color} | {color:green} master passed {color} | | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 11s {color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 59s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 53s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 53s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 46s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 22s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s {color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 28m 7s {color} | {color:green} Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 53s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 17s {color} | {color:green} hbase-client generated 0 new + 1 unchanged - 1 fixed = 1 total (was 2) {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s {color} | {color:green} hbase-server in the patch passed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 20s {color} | {color:green} hbase-client in the patch passed. {color} | | {color:red}-1{color} | {color:red} unit {color} | {color:red} 107m 24s {color} | {color:red} hbase-server in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 33s {color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 157m 27s {color} | {color:black} {color} | \\ \\ || Reason || Tests || | Timed out junit tests | org.apache.hadoop.hbase.coprocessor.TestCoprocessorMetrics | \\ \\ || Subsystem || Report/Notes || | Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:757bf37 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12873048/HBASE-18054.v4.master.patch | | JIRA Issue | HBASE-18054 | | Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck hbaseanti checkstyle compile | | uname | Linux fe759c7a4a59 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31 14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / 50e28d6 | | Default Java | 1.8.0_131 | | findbugs | v3.0.0 | | unit | https://builds.apache.org/job/PreCommit-H
[jira] [Commented] (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: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 (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16035409#comment-16035409 ] Ali commented on HBASE-18054: - [~apurtell] yes that would be better. I was thinking of adding a throwable argument to addToFailedServers() and then logging that. > 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 (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16033925#comment-16033925 ] Andrew Purtell commented on HBASE-18054: bq. Thanks. Now let's look at the patch. {code} 51 if (LOG.isDebugEnabled()) { 52LOG.debug("Added failed server with address " + address.toString() + " to list"); 53 } {code} This doesn't tell us more than we can deduce by a later log indicating the server is in the failed server list. We should add why the server has been added to the failed server list. Perhaps addToFailedServers() should get a new additional argument, a string containing the reason, that all callers can supply? > 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 (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16033491#comment-16033491 ] Hadoop QA commented on HBASE-18054: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 26s {color} | {color:blue} Docker mode activated. {color} | | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s {color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s {color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s {color} | {color:green} The patch appears to include 1 new or modified test files. {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 13s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 16s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 21s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 10s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 46s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 15s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 16s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 15s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 15s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 21s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 9s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s {color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 26m 3s {color} | {color:green} Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 53s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 16s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 32s {color} | {color:green} hbase-client in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 7s {color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 36m 42s {color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=1.13.1 Server=1.13.1 Image:yetus/hbase:757bf37 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12870834/HBASE-18054.v3.master.patch | | JIRA Issue | HBASE-18054 | | Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck hbaseanti checkstyle compile | | uname | Linux d61e6c9f9d87 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / c7a7f88 | | Default Java | 1.8.0_131 | | findbugs | v3.0.0 | | Test Results | https://builds.apache.org/job/PreCommit-HBASE-Build/7042/testReport/ | | modules | C: hbase-client U: hbase-client | | Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/7042/console | | Powered by | Apache Yetus 0.3.0 http://yetus.apache.org | This message was automatically generated. > 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, >
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16033420#comment-16033420 ] Ali commented on HBASE-18054: - [~apurtell] ASF license header added in HBASE-18054.v3.master.patch > 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 (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16032287#comment-16032287 ] Hadoop QA commented on HBASE-18054: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 32s {color} | {color:blue} Docker mode activated. {color} | | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s {color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s {color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s {color} | {color:green} The patch appears to include 1 new or modified test files. {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m 33s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 33s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 44s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 16s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 46s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 31s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 33s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 32s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 32s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 42s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 16s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s {color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 58m 10s {color} | {color:green} Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 6s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 31s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m 25s {color} | {color:green} hbase-client in the patch passed. {color} | | {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 12s {color} | {color:red} The patch generated 1 ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 77m 55s {color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:757bf37 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12870696/HBASE-18054.v2.master.patch | | JIRA Issue | HBASE-18054 | | Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck hbaseanti checkstyle compile | | uname | Linux de3c46e10452 4.8.3-std-1 #1 SMP Fri Oct 21 11:15:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / 140ce14 | | Default Java | 1.8.0_131 | | findbugs | v3.0.0 | | Test Results | https://builds.apache.org/job/PreCommit-HBASE-Build/7030/testReport/ | | asflicense | https://builds.apache.org/job/PreCommit-HBASE-Build/7030/artifact/patchprocess/patch-asflicense-problems.txt | | modules | C: hbase-client U: hbase-client | | Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/7030/console | | Powered by | Apache Yetus 0.3.0 http://yetus.apache.org | This message was automatically generated. > 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
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16030432#comment-16030432 ] Hadoop QA commented on HBASE-18054: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 43s {color} | {color:blue} Docker mode activated. {color} | | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s {color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s {color} | {color:green} The patch does not contain any @author tags. {color} | | {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s {color} | {color:red} The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m 48s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 15s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 26s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 24s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 48s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s {color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 19s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 21s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 21s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 22s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 9s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s {color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 28m 15s {color} | {color:green} Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 55s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s {color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 33s {color} | {color:green} hbase-client in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 8s {color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 43m 21s {color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=1.13.1 Server=1.13.1 Image:yetus/hbase:757bf37 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12870470/HBASE-18054.patch | | JIRA Issue | HBASE-18054 | | Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck hbaseanti checkstyle compile | | uname | Linux 9ff8409757b3 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / d547feac | | Default Java | 1.8.0_131 | | findbugs | v3.0.0 | | Test Results | https://builds.apache.org/job/PreCommit-HBASE-Build/7007/testReport/ | | modules | C: hbase-client U: hbase-client | | Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/7007/console | | Powered by | Apache Yetus 0.3.0 http://yetus.apache.org | This message was automatically generated. > 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 >Repor
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16030375#comment-16030375 ] Ali commented on HBASE-18054: - yes it works now. thank you > 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 > > > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16030370#comment-16030370 ] Andrew Purtell commented on HBASE-18054: [~aky] Try now please > 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: 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Sean Busbey >Assignee: Ali > > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16030353#comment-16030353 ] Ali commented on HBASE-18054: - [~apurtell] I cant seem to attach a patch at the moment. I think I need to be assigned this task > 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: 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Sean Busbey > > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16030348#comment-16030348 ] Andrew Purtell commented on HBASE-18054: [~aky] Did you forget to attach a patch? > 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: 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Sean Busbey > > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16029901#comment-16029901 ] Ali commented on HBASE-18054: - logging for failed server is in debug > 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: 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Sean Busbey > > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16014950#comment-16014950 ] Andrew Purtell commented on HBASE-18054: Is all logging that mentions the failed server list at DEBUG? If not then INFO would be better perhaps. > 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: 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Sean Busbey > > 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.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16011690#comment-16011690 ] Sean Busbey commented on HBASE-18054: - log at DEBUG, I guess? > 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: 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Sean Busbey > > 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.3.15#6346)