Attempt to reduce flakiness for recovery behave test on K8s (#2917)

wait until Postgres is properly started after the first crash before changing `primary_start_timeout` and killing it once again.
This commit is contained in:
Alexander Kukushkin
2023-10-17 11:27:41 +02:00
committed by GitHub
parent aa3ebe0af8
commit e513f7f127
+2
View File
@@ -14,6 +14,8 @@ Feature: recovery
Then I receive a response code 200 Then I receive a response code 200
And I receive a response role master And I receive a response role master
And I receive a response timeline 1 And I receive a response timeline 1
And "members/postgres0" key in DCS has state=running after 12 seconds
And replication works from postgres0 to postgres1 after 15 seconds
Scenario: check immediate failover when master_start_timeout=0 Scenario: check immediate failover when master_start_timeout=0
Given I issue a PATCH request to http://127.0.0.1:8008/config with {"master_start_timeout": 0} Given I issue a PATCH request to http://127.0.0.1:8008/config with {"master_start_timeout": 0}