Skip to content

Conversation

kaxil
Copy link
Member

@kaxil kaxil commented Jan 11, 2021

I think this change was unintentional -- #7205

That PR just changed it to work with breeze. Since we had 16 as default in 1.10.x
and to get better performance and keep in line with dag_concurrency and
max_active_runs_per_dag -- I think 16 makes more sense.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

I think this change was unintentional -- apache#7205

That PR just changed it to work with breeze. Since we had `16` as default in 1.10.x
and to get better performance and keep in line with `dag_concurrency` and
`max_active_runs_per_dag` -- I think `16` makes more sense.
@kaxil kaxil requested review from ashb and turbaszek January 11, 2021 12:04
Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine, but an env variable in entrypoint_ci.sh setting it to 8 should bring the stability in the tests.


## Master

### Default `[celery] worker_concurrency` is changed to `16`
Copy link
Member

@potiuk potiuk Jan 11, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we also add env variable to set the ''8" value in entrypoint_ci.sh - the number of celery workers also impacts the tests run in GitHub so it would be great to keep the lower value there to keep stability.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

worker_concurrency is not the number of workers required -- it is the number of task_instances each Celery Workers will run

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have pushed 49a71e1 to change the default for tests to 8 -- but I don't see a reason why it should be less than the default in tests

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I cannot recall exactly, we can ask @turbaszek, but I believe this was due to stability for some tests in CI that were failing intermittently (likely due to memory issues) when the worker_concurrency was too high and it was easier to change the default value rather than fix the tests (which were simply flaky)

@kaxil kaxil requested review from potiuk January 11, 2021 17:01
@github-actions
Copy link

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest master at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

@github-actions github-actions bot added the full tests needed We need to run full set of tests for this PR to merge label Jan 11, 2021
@kaxil kaxil merged commit 6c458f2 into apache:master Jan 11, 2021
@kaxil kaxil deleted the revert-concurrency branch January 11, 2021 23:41
kaxil added a commit that referenced this pull request Jan 21, 2021
This change was unintentional -- #7205

That PR just changed it to work with breeze. Since we had `16` as default in 1.10.x
and to get better performance and keep in line with `dag_concurrency` and
`max_active_runs_per_dag` -- I think `16` makes more sense.

(cherry picked from commit 6c458f2)
kaxil added a commit to astronomer/airflow that referenced this pull request Apr 12, 2021
This change was unintentional -- apache#7205

That PR just changed it to work with breeze. Since we had `16` as default in 1.10.x
and to get better performance and keep in line with `dag_concurrency` and
`max_active_runs_per_dag` -- I think `16` makes more sense.

(cherry picked from commit 6c458f2)
(cherry picked from commit 6f8f23a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full tests needed We need to run full set of tests for this PR to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants