Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation unclear about multiple LocalExecutors on HA Scheduler deployment #26565

Closed
1 of 2 tasks
vitaly-krugl opened this issue Sep 21, 2022 · 2 comments · Fixed by #32310
Closed
1 of 2 tasks

Documentation unclear about multiple LocalExecutors on HA Scheduler deployment #26565

vitaly-krugl opened this issue Sep 21, 2022 · 2 comments · Fixed by #32310

Comments

@vitaly-krugl
Copy link

vitaly-krugl commented Sep 21, 2022

What do you see as an issue?

According to Airflow documentation, it's now possible to run multiple Airflow Schedulers starting with Airflow 2.x.

What's not clear from the documentation is what happens if each of the machines running the Scheduler has executor = LocalExecutor in the [core] section of airflow.cfg. In this context, if I have Airflow Scheduler running on 3 machines, does this mean that there will also be 3 LocalExecutors processing tasks in a distributed fashion?

Solving the problem

Enhancing documentation to clarify the details about multiple LocalExecutors on HA Scheduler deployment

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@vitaly-krugl vitaly-krugl added kind:bug This is a clearly a bug kind:documentation labels Sep 21, 2022
@potiuk potiuk removed the kind:bug This is a clearly a bug label Sep 21, 2022
@potiuk
Copy link
Member

potiuk commented Sep 21, 2022

You got an explanation in #26564 (comment) - if you would like to enhance documentation - feel free to open PR. It's as easy as opening the documentation on our website and clickling "suggest a change on this page". The PR will open and you will be able to modify the docs and open a PR.

Airlfow is created by almost 2200 contribuors like you and many of them provided fixes and docs changes when they found it is missing in return for the free software they got. You are likely the best person now - since you looked for the information to formulate it and find the best place and way to describe it. Such user-provided-documentation is most valuable as we have far too many assumptions in our heads.

Looking forwar to a PR and happy to review it when ready @vitaly-krugl

@shashwata27
Copy link

@potiuk im opening the PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants