You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (Jira)" <ji...@apache.org> on 2019/12/10 21:24:00 UTC

[jira] [Closed] (AIRFLOW-1775) Remote file handler for logging

     [ https://issues.apache.org/jira/browse/AIRFLOW-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor closed AIRFLOW-1775.
--------------------------------------
    Resolution: Done

There's now a AzureBlobStore(?) log handler.

> Remote file handler for logging
> -------------------------------
>
>                 Key: AIRFLOW-1775
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1775
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: logging
>            Reporter: Niels Zeilemaker
>            Priority: Major
>
> We're using a mounted Azure file share to store our log files. Currently, Airflow is writing it's logs to that fileshare. However, this is making the solution quite expensive, as you pay per action on Azure file shares.
> If we would have a remote_file_task_logging handler, we could mimic the s3_task_logging, and copy the file to the fileshare in the close method. Reducing the cost, while still providing persistent storage.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)