From 44a6821f2a4377884046e84d0aa559e86f5c1b22 Mon Sep 17 00:00:00 2001
From: Nikita Zheleztsov <n.zheleztsov@proton.me>
Date: Thu, 24 Aug 2023 16:19:19 +0300
Subject: [PATCH] test: fix flaky gh_7515_sync_node_sees_leader_hang
The test checks, whether the instance notices leader hang during
sync. For that it stops server2 and generates some data on the
master (server1). The problem is, when connection to server3
flakes, server1 resigns and becomes read only due to fencing
enabled.
Let's disable fencing for this test, as we don't want automatic
leader resigning here.
Closes tarantool/tarantool-qa#325
NO_CHANGELOG=test
NO_DOC=test
---
.../gh_7515_sync_node_sees_leader_hang_test.lua | 1 +
1 file changed, 1 insertion(+)
diff --git a/test/replication-luatest/gh_7515_sync_node_sees_leader_hang_test.lua b/test/replication-luatest/gh_7515_sync_node_sees_leader_hang_test.lua
index 594eeba8dd..e34812ee74 100644
--- a/test/replication-luatest/gh_7515_sync_node_sees_leader_hang_test.lua
+++ b/test/replication-luatest/gh_7515_sync_node_sees_leader_hang_test.lua
@@ -9,6 +9,7 @@ local g = t.group('gh_7515_notice_leader_hang_during_sync')
g.before_each(function(cg)
cg.replica_set = replica_set:new{}
local box_cfg = {
+ election_fencing_mode = 'off',
replication_timeout = 0.1,
replication = {
server.build_listen_uri('server1', cg.replica_set.id),
--
GitLab