zalando / zalando/postgres-operator

How to set synchronous communication between primary and read-replica

Open
#2,206 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? e.g. quay.io/anuta/postgres-operator:v1.8.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
  • Are you running Postgres Operator in production? yes
  • Type of issue? question

I have a requirement to set up disaster recovery on postgresql running as a operator, I have used patroni CRD for the same for setting this up.
I need to setup asynchronous communication between the primary cluster and the standby cluster , which has been done using the below attribute .

 patroni:
   synchronous_mode: false 

Also, I need the replication between the master and read-replica synchronously in each cluster like in the below diagram, What are the modifications that I need to do in configuration files to set the primary replica communication as synchronous?

anuta-dr drawio (4)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Patroni CRD setting shown in the issue and the operator configuration for PostgreSQL replication between a primary and read-replica within one cluster. No files or tests are named; done means establishing whether synchronous intra-cluster replication is supported and documenting the exact configuration changes, or clearly identifying the limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql
Domain
databases, distributed-systems, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.