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 Thu, 05 May 2016 11:05:12 GMT

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

ASF GitHub Bot commented on FLINK-3857:

Github user rmetzger commented on the pull request:

    Thank you for opening the pull request.
    I made some inline comments.
    I don't think the proposed changes fix the issue described in the JIRA.
    I would check on each `invoke()` if `hasFailure` is set. If that's the case, you can reconnect
to EL.

> 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