[
https://issues.apache.org/jira/browse/FLINK-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064478#comment-16064478
]
ASF GitHub Bot commented on FLINK-6867:
---------------------------------------
GitHub user tzulitai opened a pull request:
https://github.com/apache/flink/pull/4191
[FLINK-6867] [elasticsearch] Fix instable Elasticsearch 1.x ITCases
The root cause for the instability in ES 1.x is that we're testing both
embedded client mode and transport client mode against the same Elasticsearch
environment. This PR ignores the embedded mode testing, as that method is
generally discouraged anyways.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tzulitai/flink FLINK-6867
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4191.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4191
----
commit ee09a7b99adbbadec584c5df1297139303f0c604
Author: Tzu-Li (Gordon) Tai <[email protected]>
Date: 2017-06-27T08:40:51Z
[FLINK-6867] [elasticsearch] Fix instable Elasticsearch 1.x ITCases
The root cause for the instability in ES 1.x is that we're testing both
embedded client mode and transport client mode against the same
Elasticsearch environment. This commit ignores the embedded mode
testing, as that method is generally discouraged anyways.
----
> Elasticsearch 1.x ITCase still instable due to embedded node instability
> ------------------------------------------------------------------------
>
> Key: FLINK-6867
> URL: https://issues.apache.org/jira/browse/FLINK-6867
> Project: Flink
> Issue Type: Bug
> Components: ElasticSearch Connector, Tests
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
>
> The integration tests for Elasticsearch 1.x seems to still be instable, being
> that the test is failing more frequently recently. One example is [1].
> The last attempt to fix this was FLINK-5772, in which the test attempts was
> increased to 3. This doesn't seem to fix the issue. In the worst scenario,
> since the root cause is an instability with Elasticsearch 1.x's embedded
> node, and ES 1.x is a very old version that is usually recommended to be
> upgraded from, we could also consider removing the IT test for ES 1.x.
> [1] https://travis-ci.org/apache/flink/jobs/240444523
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)