[
https://issues.apache.org/jira/browse/AIRFLOW-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939313#comment-16939313
]
Sampath commented on AIRFLOW-5564:
----------------------------------
[~ash] - When a task is set but Scheduler, the jobs are assigned to worker
nodes randomly(limited knowledge here). Imagine if a task like (SSH command
executions) is successful some times & fails some other time is much more bad !!
Also, thank you for quick response :)
> Feature Request to validate Airflow Connection Hook from UI
> -----------------------------------------------------------
>
> Key: AIRFLOW-5564
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5564
> Project: Apache Airflow
> Issue Type: Wish
> Components: celery, webserver, worker
> Affects Versions: 1.10.2
> Reporter: Sampath
> Priority: Major
>
> Feature Request to validate Airflow Connection Hook from UI, just like mysql
> workbench lets you test if a mysql connection is valid or not before saving.
> In a realtime scenario(airflow (webserver & scheduler) & 2-4 celery worker
> nodes) for each airflow hook, at each worker node and in each environment we
> had to this test.
> In future as we grow, there will be more connection hooks & this will keep
> increase our workload of simple yet repetitive works.
> So requesting following
> # *Airflow Connection Hooks* should have an option to validate them. At
> least for simple hooks like SSH & Mysql.
> # These tests should happen on each (Celery) *Worker* node.
> Since airflow uses paramiko, sqlachemy internally(I think) this problem can
> be quickly solvable for SSH & Mysql Hooks(starting point). If there any
> development happening in this area, kindly please point me there & then close
> this request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
