flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3857) Add reconnect attempt to Elasticsearch host
Date Tue, 07 Jun 2016 17:49:21 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318993#comment-15318993

ASF GitHub Bot commented on FLINK-3857:

Github user StephanEwen commented on the issue:

    I took a quick look at this. I am wondering if this actually needs an extra timer service
for retries.
    Can this be solved without a timer? The failures could be detected in the `invoke(...)`
method, and the retry done directly there (with some minimal backoff or so). 
    Triggering asynchronous timers is very complex and easily creates leaks, races, or leftover
work / tasks at shutdown.

> Add reconnect attempt to Elasticsearch host
> -------------------------------------------
>                 Key: FLINK-3857
>                 URL: https://issues.apache.org/jira/browse/FLINK-3857
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming Connectors
>    Affects Versions: 1.1.0, 1.0.2
>            Reporter: Fabian Hueske
>            Assignee: Subhobrata Dey
> Currently, the connection to the Elasticsearch host is opened in {{ElasticsearchSink.open()}}.
In case the connection is lost (maybe due to a changed DNS entry), the sink fails.
> I propose to catch the Exception for lost connections in the {{invoke()}} method and
try to re-open the connection for a configurable number of times with a certain delay.

This message was sent by Atlassian JIRA

View raw message