You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow for user to specify memory limits for certain containers
With the work on memory management for this release, one of the
discoveries made involved how the OOM killer on Kubelets would interact
with PostgreSQL instances (as well as pgBackRest, pgBouncer) in ways
that could lead to some undesired behavior. As such, the ability to
implicitly set memory limits was removed for the time
being.
However, there may be cases where one may want to set a memory limit,
along side a memory request + CPU request/limit to get a Guaranteed
QoS on a Pod, perhaps for pgBouncer or pgBackRest. This patch allows
for this via the `--enable-memory-limit` flag, specifically:
pgo create cluster --enable-memory-limit
pgo create cluster --enable-pgbackrest-memory-limit
pgo create cluster --enable-pgbouncer-memory-limit
pgo update cluster --enable-memory-limit
pgo update cluster --disable-memory-limit
pgo update cluster --enable-pgbackrest-memory-limit
pgo update cluster --disable-pgbackrest-memory-limit
pgo create pgbouncer --enable-memory-limit
pgo update pgbouncer --enable-memory-limit
pgo update pgbouncer --disable-memory-limit
The net effect is that if a memory request is present (and all of
PostgreSQL, pgBackRest, and pgBouncer have default values for memory
requests), the limit will also be set if it is enabled. By default, the
PostgreSQL Operator does not setting the memory limit per the behavioral
issues mentioned above.
If the memory limit is enabled, it is set to be identical to the memory
request.
This setting is also reactive, i.e. if you modify it in the CR directly,
the PostgreSQL Operator will roll out the changes to the managed Pods.
Issue: [ch8043]
Copy file name to clipboardExpand all lines: docs/content/pgo-client/reference/pgo_create_cluster.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,9 @@ pgo create cluster [flags]
25
25
--custom-config string The name of a configMap that holds custom PostgreSQL configuration files used to override defaults.
26
26
-d, --database string If specified, sets the name of the initial database that is created for the user. Defaults to the value set in the PostgreSQL Operator configuration, or if that is not present, the name of the cluster
27
27
--disable-autofail Disables autofail capabitilies in the cluster following cluster initialization.
28
+
--enable-memory-limit Enables PostgreSQL instances to be set with a memory limit on top of the memory request.
29
+
--enable-pgbackrest-memory-limit Enables the pgBackRest repository to be set with a memory limit on top of the memory request.
30
+
--enable-pgbouncer-memory-limit Enables pgBouncer instances to be set with a memory limit on top of the memory request. This has no effect if there is no pgBouncer deployment.
28
31
-h, --help help for cluster
29
32
-l, --labels string The labels to apply to this cluster.
30
33
--memory string Set the amount of RAM to request, e.g. 1GiB. Overrides the default server value.
@@ -100,4 +103,4 @@ pgo create cluster [flags]
100
103
101
104
*[pgo create](/pgo-client/reference/pgo_create/) - Create a Postgres Operator resource
102
105
103
-
###### Auto generated by spf13/cobra on 27-Apr-2020
106
+
###### Auto generated by spf13/cobra on 29-Apr-2020
0 commit comments