Parallel cluster processing

mirror of https://github.com/zalando/postgres-operator.git synced 2026-09-30 16:27:28 +02:00

Run operations concerning multiple clusters in parallel. Each cluster gets its
own worker in order to create, update, sync or delete clusters.  Each worker
acquires the lock on a cluster.  Subsequent operations on the same cluster
have to wait until the current one finishes.  There is a pool of parallel
workers, configurable with the `workers` parameter in the configmap and set by
default to 4. The cluster-related tasks  are assigned to the workers based on
a cluster name: the tasks for the same cluster will be always assigned to the
same worker. There is no blocking between workers, although there is a chance
that a single worker will become a bottleneck if too many clusters are
assigned to it; therefore, for large-scale deployments it might be necessary
to bump up workers from the default value.

This commit is contained in:

Murat Kabilov

2017-05-12 11:41:35 +02:00

parent a9c6c4861c

commit 2370659c69

13 changed files with 304 additions and 143 deletions

									
										manifests/configmap.yaml
									
		+1
		
												View File
												
				@@ -28,3 +28,4 @@ data:

				  resync_period_pod: 5m

				  super_username: postgres

				  teams_api_url: https://teams.example.com/api/

				  workers: "4"