[jira] [Commented] (AIRFLOW-6522) Sensors in reschedule mode with S3TaskHandler can cause log duplication
[
https://issues.apache.org/jira/browse/AIRFLOW-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028393#comment-17028393
]
ASF subversion and git services commented on AIRFLOW-6522:
--
Commit c7ad2c3f1a5c3fd46edbbc390b1229e01e64 in airflow's branch
refs/heads/v1-10-test from rconroy293
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=c7ad2c3 ]
[AIRFLOW-6522] Clear task log file before starting to fix duplication in
S3TaskHandler (#7120)
The same task instance (including try number) can be run on a worker
when using a sensor in "reschedule" mode. Accordingly, this clears the
local log file when re-initializing the logger so that the old log
lines aren't uploaded again when the logger is closed.
(cherry picked from commit 88608caa56bf3621807af860a6a378242220de47)
> Sensors in reschedule mode with S3TaskHandler can cause log duplication
> ---
>
> Key: AIRFLOW-6522
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6522
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.10.6
>Reporter: Robert Conroy
>Assignee: Robert Conroy
>Priority: Minor
> Fix For: 1.10.8
>
>
> With sensors using {{reschedule}} mode and {{S3TaskHandler}} for logging, the
> task instance log gets a bunch of duplicate messages. I believe this is
> happening because contents of the local log file are appended to what's
> already in S3. The local log file may contain log messages that have already
> been uploaded to S3 if the task is sent back to a worker that had already
> processed a poke for that task instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6522) Sensors in reschedule mode with S3TaskHandler can cause log duplication
[
https://issues.apache.org/jira/browse/AIRFLOW-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023800#comment-17023800
]
ASF subversion and git services commented on AIRFLOW-6522:
--
Commit a9190f7b71fd26daf8565ed6aae4107270248469 in airflow's branch
refs/heads/v1-10-test from rconroy293
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=a9190f7 ]
[AIRFLOW-6522] Clear task log file before starting to fix duplication in
S3TaskHandler (#7120)
The same task instance (including try number) can be run on a worker
when using a sensor in "reschedule" mode. Accordingly, this clears the
local log file when re-initializing the logger so that the old log
lines aren't uploaded again when the logger is closed.
(cherry picked from commit 88608caa56bf3621807af860a6a378242220de47)
> Sensors in reschedule mode with S3TaskHandler can cause log duplication
> ---
>
> Key: AIRFLOW-6522
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6522
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.10.6
>Reporter: Robert Conroy
>Assignee: Robert Conroy
>Priority: Minor
> Fix For: 1.10.8
>
>
> With sensors using {{reschedule}} mode and {{S3TaskHandler}} for logging, the
> task instance log gets a bunch of duplicate messages. I believe this is
> happening because contents of the local log file are appended to what's
> already in S3. The local log file may contain log messages that have already
> been uploaded to S3 if the task is sent back to a worker that had already
> processed a poke for that task instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6522) Sensors in reschedule mode with S3TaskHandler can cause log duplication
[
https://issues.apache.org/jira/browse/AIRFLOW-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022412#comment-17022412
]
ASF subversion and git services commented on AIRFLOW-6522:
--
Commit c7ad2c3f1a5c3fd46edbbc390b1229e01e64 in airflow's branch
refs/heads/v1-10-test from rconroy293
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=c7ad2c3 ]
[AIRFLOW-6522] Clear task log file before starting to fix duplication in
S3TaskHandler (#7120)
The same task instance (including try number) can be run on a worker
when using a sensor in "reschedule" mode. Accordingly, this clears the
local log file when re-initializing the logger so that the old log
lines aren't uploaded again when the logger is closed.
(cherry picked from commit 88608caa56bf3621807af860a6a378242220de47)
> Sensors in reschedule mode with S3TaskHandler can cause log duplication
> ---
>
> Key: AIRFLOW-6522
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6522
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.10.6
>Reporter: Robert Conroy
>Assignee: Robert Conroy
>Priority: Minor
> Fix For: 1.10.8
>
>
> With sensors using {{reschedule}} mode and {{S3TaskHandler}} for logging, the
> task instance log gets a bunch of duplicate messages. I believe this is
> happening because contents of the local log file are appended to what's
> already in S3. The local log file may contain log messages that have already
> been uploaded to S3 if the task is sent back to a worker that had already
> processed a poke for that task instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6522) Sensors in reschedule mode with S3TaskHandler can cause log duplication
[
https://issues.apache.org/jira/browse/AIRFLOW-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015094#comment-17015094
]
ASF GitHub Bot commented on AIRFLOW-6522:
-
ashb commented on pull request #7120: [AIRFLOW-6522] Clear log file to fix
duplication in S3TaskHandler
URL: https://github.com/apache/airflow/pull/7120
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Sensors in reschedule mode with S3TaskHandler can cause log duplication
> ---
>
> Key: AIRFLOW-6522
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6522
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.10.6
>Reporter: Robert Conroy
>Assignee: Robert Conroy
>Priority: Minor
>
> With sensors using {{reschedule}} mode and {{S3TaskHandler}} for logging, the
> task instance log gets a bunch of duplicate messages. I believe this is
> happening because contents of the local log file are appended to what's
> already in S3. The local log file may contain log messages that have already
> been uploaded to S3 if the task is sent back to a worker that had already
> processed a poke for that task instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6522) Sensors in reschedule mode with S3TaskHandler can cause log duplication
[
https://issues.apache.org/jira/browse/AIRFLOW-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015095#comment-17015095
]
ASF subversion and git services commented on AIRFLOW-6522:
--
Commit 88608caa56bf3621807af860a6a378242220de47 in airflow's branch
refs/heads/master from rconroy293
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=88608ca ]
[AIRFLOW-6522] Clear task log file before starting to fix duplication in
S3TaskHandler (#7120)
The same task instance (including try number) can be run on a worker
when using a sensor in "reschedule" mode. Accordingly, this clears the
local log file when re-initializing the logger so that the old log
lines aren't uploaded again when the logger is closed.
> Sensors in reschedule mode with S3TaskHandler can cause log duplication
> ---
>
> Key: AIRFLOW-6522
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6522
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.10.6
>Reporter: Robert Conroy
>Assignee: Robert Conroy
>Priority: Minor
>
> With sensors using {{reschedule}} mode and {{S3TaskHandler}} for logging, the
> task instance log gets a bunch of duplicate messages. I believe this is
> happening because contents of the local log file are appended to what's
> already in S3. The local log file may contain log messages that have already
> been uploaded to S3 if the task is sent back to a worker that had already
> processed a poke for that task instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6522) Sensors in reschedule mode with S3TaskHandler can cause log duplication
[
https://issues.apache.org/jira/browse/AIRFLOW-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012324#comment-17012324
]
ASF GitHub Bot commented on AIRFLOW-6522:
-
rconroy293 commented on pull request #7120: [AIRFLOW-6522] Clear log file to
fix duplication in S3TaskHandler
URL: https://github.com/apache/airflow/pull/7120
The same task instance (including try number) can be run on a worker
when using a sensor in "reschedule" mode. Accordingly, this clears the
local log file when re-initializing the logger so that the old log
lines aren't uploaded again when the logger is closed.
---
Issue link: WILL BE INSERTED BY
[boring-cyborg](https://github.com/kaxil/boring-cyborg)
- [ ] Description above provides context of the change
- [ ] Commit message/PR title starts with `[AIRFLOW-]`. AIRFLOW- =
JIRA ID*
- [ ] Unit tests coverage for changes (not needed for documentation changes)
- [ ] Commits follow "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)"
- [ ] Relevant documentation is updated including usage instructions.
- [ ] I will engage committers as explained in [Contribution Workflow
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
* For document-only changes commit message can start with
`[AIRFLOW-]`.
---
In case of fundamental code change, Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
Read the [Pull Request
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)
for more information.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Sensors in reschedule mode with S3TaskHandler can cause log duplication
> ---
>
> Key: AIRFLOW-6522
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6522
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.10.6
>Reporter: Robert Conroy
>Assignee: Robert Conroy
>Priority: Minor
>
> With sensors using {{reschedule}} mode and {{S3TaskHandler}} for logging, the
> task instance log gets a bunch of duplicate messages. I believe this is
> happening because contents of the local log file are appended to what's
> already in S3. The local log file may contain log messages that have already
> been uploaded to S3 if the task is sent back to a worker that had already
> processed a poke for that task instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
