[
https://issues.apache.org/jira/browse/AIRFLOW-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873973#comment-16873973
]
ASF subversion and git services commented on AIRFLOW-3502:
----------------------------------------------------------
Commit f6f37f207aadcbc31a66f045f92ea448df094da7 in airflow's branch
refs/heads/v1-10-test from Xiaodong
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=f6f37f2 ]
[AIRFLOW-3502] Update config template to reflect supporting different Celery
pool implementation (#5477)
The support to different Celery pool implementation has been added
in https://github.com/apache/airflow/pull/4308.
But it's not reflected in the default_airflow.cfg yet, while it's
the main portal of config options to most users.
(cherry picked from commit dd08ae3469a50a145f9ae7f819ed1840fe2a5bd6)
> Add config option to control celery pool used
> ---------------------------------------------
>
> Key: AIRFLOW-3502
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3502
> Project: Apache Airflow
> Issue Type: Improvement
> Components: celery
> Affects Versions: 1.10.0
> Reporter: Gabriel Silk
> Assignee: Gabriel Silk
> Priority: Minor
> Fix For: 1.10.4
>
>
> This adds a config option for the "pool" to allow uses to specify "prefork"
> vs "solo" etc. This is particularly useful with infrastructures that don't
> play nicely with celery's default prefork multi-processing model.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
