Skip to content

[AIRFLOW-1077] Warn about subdag deadlock case#2367

Closed
akosel wants to merge 1 commit intoapache:masterfrom
akosel:airflow-1077
Closed

[AIRFLOW-1077] Warn about subdag deadlock case#2367
akosel wants to merge 1 commit intoapache:masterfrom
akosel:airflow-1077

Conversation

@akosel
Copy link
Contributor

@akosel akosel commented Jun 15, 2017

Dear Airflow maintainers,

Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!

JIRA

Description

  • Here are some details about my PR, including screenshots of any UI changes:

Addresses a case that may be counter-intuitive to users where a subdag count greater than the concurrency limit can lead to deadlock. It also suggests a workaround for dealing with this issue.

Tests

  • My PR adds the following unit tests OR does not need testing for this extremely good reason:

It's a comment so there isn't anything to test.

Commits

  • My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

@mention-bot
Copy link

@akosel, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mistercrunch, @jlowin and @AntoineAugusti to be potential reviewers.

@akosel akosel changed the title Warn about subdag deadlock case [AIRFLOW-1077] Warn about subdag deadlock case Jun 15, 2017
Copy link
Contributor

Choose a reason for hiding this comment

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

The capitalization is all over the place in this doc, let's stick with "SubDag" since that is what is in code.

@saguziel
Copy link
Contributor

I think you should create a new issue for this rather than use that one

@tispratik
Copy link

I think i am running into the same issue. Airflow says the subdags are running, but none of the steps within it are executing. When i restarted airflow, some progress happened, but then it got blocked again.

@codecov-io
Copy link

Codecov Report

Merging #2367 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #2367   +/-   ##
======================================
  Coverage      71%     71%           
======================================
  Files         150     150           
  Lines       11740   11740           
======================================
  Hits         8336    8336           
  Misses       3404    3404

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e52070...af32a54. Read the comment docs.

@SamWildmo
Copy link

I think i also encountered this but it happened once so i cant be sure.

@yegeniy
Copy link
Contributor

yegeniy commented Oct 30, 2018

This is a great warning for those who are not on the latest version, but the default executor for SubDags is now the SequentialExecutor.

@SamWildmo
Copy link

@yegeiny if someone can overwrite it to local executor then this PR is still needed. If not then maybe commiters should close this.

@yegeniy
Copy link
Contributor

yegeniy commented Oct 31, 2018

Great point. I think it's still totally over-writeable.

@stale
Copy link

stale bot commented Dec 15, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Dec 15, 2018
@stale stale bot closed this Dec 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Stale PRs per the .github/workflows/stale.yml policy file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants