[
https://issues.apache.org/jira/browse/AIRFLOW-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731256#comment-16731256
]
jack commented on AIRFLOW-1161:
-------------------------------
But this is exactly what Airflow provides... If the task fails it will retry.
Are you requesting that the hook will have an inner retry loop?
> HttpHook shall be configurable to non-status errors
> ---------------------------------------------------
>
> Key: AIRFLOW-1161
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1161
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Deo
> Priority: Major
>
> When using HttpSensor, which underlying would use HttpHook to perform the
> request. If the target service is down, which refused the connection, the
> task would fail immediately.
> would be great if this behaviour is configurable, so the sensor would keep
> sensoring until the service is up again.
> traceback of the error:
> [2017-04-29 02:00:31,248] {base_task_runner.py:95} INFO - Subtask:
> requests.exceptions.ConnectionError: HTTPConnectionPool(host='xxxx',
> port=123): Max retries exceeded with url: /xxxx (Caused by
> NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection
> object at 0x7f94b64b44e0>: Failed to establish a new connection: [Errno 111]
> Connection refused',))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
