check-patroni/tests/json/cluster_has_replica_patroni_verion_3.1.0.json

{
  "state": "running",
  "postmaster_start_time": "2021-08-11 07:02:20.732 UTC",
  "role": "master",
  "server_version": 110012,
  "cluster_unlocked": false,
  "xlog": {
    "location": 1174407088
  },
  "timeline": 51,
  "replication": [
    {
      "usename": "replicator",
      "application_name": "srv1",
      "client_addr": "10.20.199.3",
      "state": "streaming",
      "sync_state": "async",
      "sync_priority": 0
    }
  ],
  "database_system_identifier": "6965971025273547206",
  "patroni": {
    "version": "3.1.0",
    "scope": "patroni-demo"
  }
}
cluster_has_replica: fix the way a healthy replica is detected For patroni >= version 3.0.4: * the role is `replica` or `sync_standby` * the state is `streaming` or `in archive recovery` * the timeline is the same as the leader * the lag is lower or equal to `max_lag` For prio versions of patroni: * the role is `replica` or `sync_standby` * the state is `running` * the timeline is the same as the leader * the lag is lower or equal to `max_lag` Additionnally, we now display the timeline in the perfstats. We also try to display the perf stats of unhealthy replica as much as possible. Update tests for cluster_has_replica: * Fix the tests to make them work with the new algotithm * Add a specific test for tl divergences 2023-09-27 16:37:40 +02:00			`{`
			`"state": "running",`
			`"postmaster_start_time": "2021-08-11 07:02:20.732 UTC",`
			`"role": "master",`
			`"server_version": 110012,`
			`"cluster_unlocked": false,`
			`"xlog": {`
			`"location": 1174407088`
			`},`
			`"timeline": 51,`
			`"replication": [`
			`{`
			`"usename": "replicator",`
			`"application_name": "srv1",`
			`"client_addr": "10.20.199.3",`
			`"state": "streaming",`
			`"sync_state": "async",`
			`"sync_priority": 0`
			`}`
			`],`
			`"database_system_identifier": "6965971025273547206",`
			`"patroni": {`
			`"version": "3.1.0",`
			`"scope": "patroni-demo"`
			`}`
			`}`