kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a...@apache.org
Subject [kudu] branch master updated: ksck_remote-test: deflake some more
Date Thu, 28 Mar 2019 04:40:52 GMT
This is an automated email from the ASF dual-hosted git repository.

adar pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/master by this push:
     new e34b410  ksck_remote-test: deflake some more
e34b410 is described below

commit e34b410d215e9485f0b60c25b348a3b512a12b3c
Author: Adar Dembo <adar@cloudera.com>
AuthorDate: Mon Mar 25 23:15:26 2019 -0700

    ksck_remote-test: deflake some more
    
    Apparently fixing KUDU-2748 wasn't enough, and there are still some cases
    where the consensus state isn't the same across all masters after they are
    restarted, likely due to KUDU-2709. Maybe this will do the trick?
    
    Change-Id: I2cc6c98f91703b52dbf099b1f544a2c70099f35b
    Reviewed-on: http://gerrit.cloudera.org:8080/12853
    Tested-by: Kudu Jenkins
    Reviewed-by: Alexey Serbin <aserbin@cloudera.com>
---
 src/kudu/tools/ksck_remote-test.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/kudu/tools/ksck_remote-test.cc b/src/kudu/tools/ksck_remote-test.cc
index ffce813..edbe060 100644
--- a/src/kudu/tools/ksck_remote-test.cc
+++ b/src/kudu/tools/ksck_remote-test.cc
@@ -538,6 +538,7 @@ TEST_F(RemoteKsckTest, TestClusterWithLocation) {
   // TODO(KUDU-2709): remove ASSERT_EVENTUALLY around CheckMasterConsensus
   //                  when KUDU-2709 is addressed.
   ASSERT_EVENTUALLY([&]() {
+    ASSERT_OK(ksck_->CheckMasterHealth()); // Need to refresh master cstate.
     ASSERT_OK(ksck_->CheckMasterConsensus());
   });
   ASSERT_EVENTUALLY([&]() {


Mime
View raw message