From 913170e16af2d953e8dc366c5419c0f1bbc018a9 Mon Sep 17 00:00:00 2001 From: prha Date: Thu, 19 Dec 2024 11:46:22 -0800 Subject: [PATCH] edit --- .../content/guides/limiting-concurrency-in-data-pipelines.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx index 89162fac96199..6f97af98978a9 100644 --- a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx +++ b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx @@ -422,8 +422,8 @@ The concurrency key should match the name that the op/asset is tagged with. For A default concurrency limit can be configured for the instance, for any concurrency keys that do not have an explicit limit set: -- **Dagster+**: Use the deployment settings via the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] -- **Dagster Open Source**: Use your instance's `dagster.yaml` +- **Dagster+**: Edit the `concurrency` config in deployment settings via the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] +- **Dagster Open Source**: Edit the `concurrency` config in your instance's `dagster.yaml` To enable this default value, use `concurrency.default_op_concurrency_limit`. For example, the following would set the default concurrency value for the deployment to 1: