[
https://issues.apache.org/jira/browse/AIRFLOW-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155224#comment-16155224
]
ASF subversion and git services commented on AIRFLOW-1562:
----------------------------------------------------------
Commit 32750601ad0a422283613bf7fccff8eb5407bc9c in incubator-airflow's branch
refs/heads/master from [~Fokko]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=3275060 ]
[AIRFLOW-1562] Spark-sql logging contains deadlock
Logging in SparkSqlOperator does not work as
intended. Spark-sql
internally redirects all logs to stdout (including
stderr),
which causes the current two iterator logging to
get stuck with
the stderr pipe. This situation can lead to a
deadlock
because the std-err can grow too big and it will
start to block
until it will be consumed, which will only happen
when the process
ends, so the process stalls.
Closes #2563 from Fokko/AIRFLOW-1562-Spark-sql-
loggin-contains-deadlock
> Spark-sql deadlock in logging
> -----------------------------
>
> Key: AIRFLOW-1562
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1562
> Project: Apache Airflow
> Issue Type: Bug
> Components: hooks
> Affects Versions: Airflow 1.8
> Reporter: Fokko Driesprong
>
> Related to Issue 1255
> Logging in SparkSqlOperator does not work as intended (continuous logging as
> received in the subprocess). This is because, spark-sql internally redirects
> all logs to stdout (including stderr), which causes the current two iterator
> logging to get stuck with empty stderr pipe. Also this situation can lead to
> a deadlock because the std-err can grow too big and it will start to block
> until it gets consumed, which will only happen when the process ends, so the
> process stalls.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
