bitterfox commented on pull request #3068:
URL: https://github.com/apache/hbase/pull/3068#issuecomment-803726203


   Thank you for your help. Pushed checkstyle fix, hope the next check passes.
   
   Following unit tests passed locally.
   
   ```
   [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
7.562 s <<< FAILURE! - in 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers
   [ERROR] 
testChangingNumberOfPeerRegionServers(org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers)
  Time elapsed: 3.913 s  <<< ERROR!
   org.apache.hadoop.hbase.client.RetriesExhaustedException: 
   Failed after attempts=6, exceptions:
   Fri Mar 19 07:35:57 UTC 2021, 
RpcRetryingCaller{globalStartTime=1616139357578, pause=100, retries=6}, 
java.io.IOException: Call to cf301fc9ce7b:40869 failed on local exception: 
java.io.EOFException
   Fri Mar 19 07:35:57 UTC 2021, 
RpcRetryingCaller{globalStartTime=1616139357578, pause=100, retries=6}, 
java.net.ConnectException: Call to cf301fc9ce7b:40869 failed on connection 
exception: java.net.ConnectException: Connection refused
   Fri Mar 19 07:35:57 UTC 2021, 
RpcRetryingCaller{globalStartTime=1616139357578, pause=100, retries=6}, 
java.io.IOException: Call to cf301fc9ce7b:40869 failed on local exception: 
org.apache.hadoop.hbase.ipc.FailedServerException: This server is in the failed 
servers list: cf301fc9ce7b:40869
   Fri Mar 19 07:35:58 UTC 2021, 
RpcRetryingCaller{globalStartTime=1616139357578, pause=100, retries=6}, 
java.io.IOException: Call to cf301fc9ce7b:40869 failed on local exception: 
org.apache.hadoop.hbase.ipc.FailedServerException: This server is in the failed 
servers list: cf301fc9ce7b:40869
   Fri Mar 19 07:35:58 UTC 2021, 
RpcRetryingCaller{globalStartTime=1616139357578, pause=100, retries=6}, 
java.io.IOException: Call to cf301fc9ce7b:40869 failed on local exception: 
org.apache.hadoop.hbase.ipc.FailedServerException: This server is in the failed 
servers list: cf301fc9ce7b:40869
   Fri Mar 19 07:35:59 UTC 2021, 
RpcRetryingCaller{globalStartTime=1616139357578, pause=100, retries=6}, 
java.net.ConnectException: Call to cf301fc9ce7b:40869 failed on connection 
exception: java.net.ConnectException: Connection refused
   
        at 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers.doPutTest(TestReplicationChangingPeerRegionservers.java:131)
        at 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers.testChangingNumberOfPeerRegionServers(TestReplicationChangingPeerRegionservers.java:105)
   Caused by: java.net.ConnectException: Call to cf301fc9ce7b:40869 failed on 
connection exception: java.net.ConnectException: Connection refused
        at 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers.doPutTest(TestReplicationChangingPeerRegionservers.java:131)
        at 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers.testChangingNumberOfPeerRegionServers(TestReplicationChangingPeerRegionservers.java:105)
   Caused by: java.net.ConnectException: Connection refused
        at 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers.doPutTest(TestReplicationChangingPeerRegionservers.java:131)
        at 
org.apache.hadoop.hbase.replication.TestReplicationChangingPeerRegionservers.testChangingNumberOfPeerRegionServers(TestReplicationChangingPeerRegionservers.java:105)
   ```
   
   ```
   [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
17.662 s <<< FAILURE! - in 
org.apache.hadoop.hbase.master.TestRegionsRecoveryConfigManager
   [ERROR] 
testChoreSchedule(org.apache.hadoop.hbase.master.TestRegionsRecoveryConfigManager)
  Time elapsed: 17.62 s  <<< FAILURE!
   java.lang.AssertionError
        at 
org.apache.hadoop.hbase.master.TestRegionsRecoveryConfigManager.testChoreSchedule(TestRegionsRecoveryConfigManager.java:99)
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to