AWS emr: Clarify default per-virtual-cluster concurrency limit behavior
Summary
Documentation updated to state the default per-virtual-cluster concurrency limit is 1000 concurrent job runs and that empty schedulerConfiguration resets to that default.
Security assessment
Clarifies default resource-limit behavior; relates to availability/overload prevention but is not a security control change.
Evidence
+To remove your custom limits from a virtual cluster, pass an empty `schedulerConfiguration`. This clears the values that you configured. The per-virtual-cluster concurrency limit then returns to its default of 1000 concurrent job runs. Note that _omitting_ `schedulerConfiguration` from the request instead leaves the existing limits unchanged — you must pass an empty object to clear them.
Diff
diff --git a/emr/latest/EMR-on-EKS-DevelopmentGuide/virtual-cluster.md b/emr/latest/EMR-on-EKS-DevelopmentGuide/virtual-cluster.md index 1cffc8e..df1f399 100644 --- a//emr/latest/EMR-on-EKS-DevelopmentGuide/virtual-cluster.md +++ b//emr/latest/EMR-on-EKS-DevelopmentGuide/virtual-cluster.md @@ -166 +166 @@ To change limits on an existing virtual cluster, use the `update-virtual-cluster -To remove the limits from a virtual cluster, pass an empty `schedulerConfiguration`. This clears the configuration, so no limits apply and the virtual cluster returns to default (unlimited) behavior. Note that _omitting_ `schedulerConfiguration` from the request instead leaves the existing limits unchanged — you must pass an empty object to clear them. +To remove your custom limits from a virtual cluster, pass an empty `schedulerConfiguration`. This clears the values that you configured. The per-virtual-cluster concurrency limit then returns to its default of 1000 concurrent job runs. Note that _omitting_ `schedulerConfiguration` from the request instead leaves the existing limits unchanged — you must pass an empty object to clear them. @@ -213 +213 @@ The right limits depend on three things: how much work your Amazon EKS cluster c - * No limits are applied by default. Existing virtual clusters and workloads are unaffected unless you explicitly set `schedulerConfiguration`. + * By default, the per-virtual-cluster concurrency limit is set to 1000 concurrent job runs. This default helps prevent too many jobs from overloading the cluster. You can override the default by setting `maxConcurrentJobRuns` in the virtual cluster's `schedulerConfiguration`. The values in the earlier examples, such as 500, are sample overrides rather than the default.