mirror of
https://github.com/outbackdingo/patroni.git
synced 2026-08-25 14:53:37 +00:00
Alexander KukushkinandGitHub
4c3af2d1a0
keep as much backward compatibility as possible.
Following changes were made:
1. All internal checks are performed as `role in ('master', 'primary')`
2. All internal variables/functions/methods are renamed
3. `GET /metrics` endpoint returns `patroni_primary` in addition to `patroni_master`.
4. Logs are changed to use leader/primary/member/remote depending on the context
5. Unit-tests are using only role = 'primary' instead of 'master' to verify that 1 works.
6. patronictl still supports old syntax, but also accepts `--leader` and `--primary`.
7. `master_(start|stop)_timeout` is automatically translated to `primary_(start|stop)_timeout` if the last one is not set.
8. updated the documentation and some examples
Future plan: in the next major release switch role name from `master` to `primary` and maybe drop `master` altogether.
The Kubernetes implementation will require more work and keep two labels in parallel. Label values should probably be configurable as described in https://github.com/zalando/patroni/issues/2495.
62 lines
4.3 KiB
Gherkin
62 lines
4.3 KiB
Gherkin
Feature: ignored slots
|
|
Scenario: check ignored slots aren't removed on failover/switchover
|
|
Given I start postgres1
|
|
Then postgres1 is a leader after 10 seconds
|
|
And there is a non empty initialize key in DCS after 15 seconds
|
|
When I issue a PATCH request to http://127.0.0.1:8009/config with {"ignore_slots": [{"name": "unmanaged_slot_0", "database": "postgres", "plugin": "test_decoding", "type": "logical"}, {"name": "unmanaged_slot_1", "database": "postgres", "plugin": "test_decoding"}, {"name": "unmanaged_slot_2", "database": "postgres"}, {"name": "unmanaged_slot_3"}], "postgresql": {"parameters": {"wal_level": "logical"}}}
|
|
Then I receive a response code 200
|
|
And Response on GET http://127.0.0.1:8009/config contains ignore_slots after 10 seconds
|
|
# Make sure the wal_level has been changed.
|
|
When I shut down postgres1
|
|
And I start postgres1
|
|
Then postgres1 is a leader after 10 seconds
|
|
And "members/postgres1" key in DCS has role=master after 3 seconds
|
|
# Make sure Patroni has finished telling Postgres it should be accepting writes.
|
|
And postgres1 role is the primary after 20 seconds
|
|
# 1. Create our test logical replication slot.
|
|
# Test that ny subset of attributes in the ignore slots matcher is enough to match a slot
|
|
# by using 3 different slots.
|
|
When I create a logical replication slot unmanaged_slot_0 on postgres1 with the test_decoding plugin
|
|
And I create a logical replication slot unmanaged_slot_1 on postgres1 with the test_decoding plugin
|
|
And I create a logical replication slot unmanaged_slot_2 on postgres1 with the test_decoding plugin
|
|
And I create a logical replication slot unmanaged_slot_3 on postgres1 with the test_decoding plugin
|
|
And I create a logical replication slot dummy_slot on postgres1 with the test_decoding plugin
|
|
# It seems like it'd be obvious that these slots exist since we just created them,
|
|
# but Patroni can actually end up dropping them almost immediately, so it's helpful
|
|
# to verify they exist before we begin testing whether they persist through failover
|
|
# cycles.
|
|
Then postgres1 has a logical replication slot named unmanaged_slot_0 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_1 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_2 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_3 with the test_decoding plugin
|
|
|
|
When I start postgres0
|
|
Then "members/postgres0" key in DCS has role=replica after 3 seconds
|
|
And postgres0 role is the secondary after 20 seconds
|
|
# Verify that the replica has advanced beyond the point in the WAL
|
|
# where we created the replication slot so that on the next failover
|
|
# cycle we don't accidentally rewind to before the slot creation.
|
|
And replication works from postgres1 to postgres0 after 20 seconds
|
|
When I shut down postgres1
|
|
Then "members/postgres0" key in DCS has role=master after 3 seconds
|
|
|
|
# 2. After a failover the server (now a replica) still has the slot.
|
|
When I start postgres1
|
|
Then postgres1 role is the secondary after 20 seconds
|
|
And "members/postgres1" key in DCS has role=replica after 3 seconds
|
|
# give Patroni time to sync replication slots
|
|
And I sleep for 2 seconds
|
|
And postgres1 has a logical replication slot named unmanaged_slot_0 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_1 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_2 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_3 with the test_decoding plugin
|
|
And postgres1 does not have a logical replication slot named dummy_slot
|
|
|
|
# 3. After a failover the server (now a primary) still has the slot.
|
|
When I shut down postgres0
|
|
Then "members/postgres1" key in DCS has role=master after 3 seconds
|
|
And postgres1 has a logical replication slot named unmanaged_slot_0 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_1 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_2 with the test_decoding plugin
|
|
And postgres1 has a logical replication slot named unmanaged_slot_3 with the test_decoding plugin
|