airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-2895) Prevent scheduler from spamming heartbeats/logs
Date Mon, 13 Aug 2018 18:03:00 GMT


ASF GitHub Bot commented on AIRFLOW-2895:

aoen opened a new pull request #3747: [AIRFLOW-2895] Prevent scheduler from spamming heartbeats/logs
   Reverts most of AIRFLOW-2027 until the issues with it can be fixed.
   ### Jira
   - [X] My PR addresses the following [Airflow Jira](
issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
   ### Description
   - [X] Here are some details about my PR, including screenshots of any UI changes:
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   Reverting some broken code that is missing tests.
   ### Commits
   - [X] 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
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   ### Documentation
   - [X] In case of new functionality, my PR adds documentation that describes how to use
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   ### Code Quality
   - [X] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Prevent scheduler from spamming heartbeats/logs
> -----------------------------------------------
>                 Key: AIRFLOW-2895
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>            Priority: Major
> There seems to be a couple of problems with []
that cause the sleep to not trigger and Scheduler heartbeating/logs to be spammed:
>  # If all of the files are being processed in the queue, there is no sleep (can be fixed
by sleeping for min_sleep even if there are no files)
>  # I have heard reports that some files can return a parsing time that is monotonically
increasing for some reason (e.g. file actually parses in 1s each loop, but the reported duration
seems to use the very time the file was parsed as the start time instead of the last time),
I haven't confirmed this but it sounds problematic.
> To unblock the release I'm reverting this PR for now. It should be re-added with tests/mocking.

This message was sent by Atlassian JIRA

View raw message