Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

synchronous_node_count support #1484

Merged
merged 8 commits into from Feb 25, 2022
Merged

synchronous_node_count support #1484

merged 8 commits into from Feb 25, 2022

Conversation

Menzorg
Copy link
Contributor

@Menzorg Menzorg commented May 5, 2021

patroni synchronous_node_count support #1479

@Menzorg
Copy link
Contributor Author

Menzorg commented May 5, 2021

Not full tested, but builded and checked with SELECT * FROM pg_stat_replication;

@@ -254,6 +254,8 @@ explanation of `ttl` and `loop_wait` parameters.
* **synchronous_mode_strict**
Patroni `synchronous_mode_strict` parameter value. Can be used in addition to `synchronous_mode`. The default is set to `false`. Optional.

* **synchronous_node_count**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should add the info here that it's only available for Spilo images with Patroni 2.0+

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be right here at 257 or in description in 258?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I add ❗ before notification?

@FxKu FxKu added this to the 1.7 milestone May 14, 2021
@@ -298,6 +298,7 @@ var unmarshalCluster = []struct {
LoopWait: 10,
RetryTimeout: 10,
MaximumLagOnFailover: 33554432,
SynchronousNodeCount: 1,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not enough here. You have to introduce synchronous_node_count option in all the other expected output examples, e.g. search for maximum_lag_on_failover and you find the places I mean.

Copy link
Contributor Author

@Menzorg Menzorg Oct 2, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. I introduced synchronous_node_count in all places, where i can find synchronous_mode. If i will try to search maximum_lag_on_failover there is only one place where i did not intoduced synchronous_node_count.
It is pkg/apis/acid.zalan.do/v1/util_test.go in a place like this
But i dont understand is it the right place to introduce synchronous_node_count. Could you help, please? What should i do to help to introduce it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you run the unit tests with make test or go test ./... you should be able to see where unit tests are failing

@FxKu FxKu modified the milestones: 1.7, 1.8 Aug 9, 2021
pkg/cluster/k8sres_test.go Outdated Show resolved Hide resolved
@FxKu
Copy link
Member

FxKu commented Feb 25, 2022

👍

1 similar comment
@jopadi
Copy link
Member

jopadi commented Feb 25, 2022

👍

@FxKu FxKu merged commit 06c28da into zalando:master Feb 25, 2022
@FxKu
Copy link
Member

FxKu commented Feb 25, 2022

Thanks again @Menzorg !

cstohr1 pushed a commit to cstohr1/postgres-operator that referenced this pull request Feb 29, 2024
CRD support was previously added in zalando#1484, but comparing desired SynchronousNodeCount to the actual patroni config was missing
cstohr1 added a commit to cstohr1/postgres-operator that referenced this pull request Feb 29, 2024
CRD support was previously added in zalando#1484, but comparing desired SynchronousNodeCount to the actual patroni config was missing
cstohr1 added a commit to cstohr1/postgres-operator that referenced this pull request Feb 29, 2024
CRD support for synchronous_node_count was previously added in zalando#1484, however the desired SynchronousNodeCount was not compared to the actual patroni configuration, which meant it was never updated.
FxKu pushed a commit that referenced this pull request Mar 5, 2024
CRD support for synchronous_node_count was previously added in #1484, however the desired SynchronousNodeCount was not compared to the actual patroni configuration, which meant it was never updated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants