You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Etienne Chauchot (JIRA)" <ji...@apache.org> on 2019/01/16 14:32:00 UTC
[jira] [Comment Edited] (BEAM-6279) Failures in
ElasticSearchIOTest: testWriteRetryValidRequest (versions 2 & 5)
testDefaultRetryPredicate (version 5)
[ https://issues.apache.org/jira/browse/BEAM-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744096#comment-16744096 ]
Etienne Chauchot edited comment on BEAM-6279 at 1/16/19 2:31 PM:
-----------------------------------------------------------------
[~kenn] as you're cutting the release branch, should I target the fix to 2.10 and cherry pick commits to 2.10 release branch ?
was (Author: echauchot):
[~kenn] should I target the fix to 2.10 and cherry pick commits to 2.10 release branch ?
> Failures in ElasticSearchIOTest: testWriteRetryValidRequest (versions 2 & 5) testDefaultRetryPredicate (version 5)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-6279
> URL: https://issues.apache.org/jira/browse/BEAM-6279
> Project: Beam
> Issue Type: Bug
> Components: io-java-elasticsearch, test-failures
> Reporter: Kenneth Knowles
> Assignee: Tim Robertson
> Priority: Critical
> Labels: flake
> Fix For: 2.11.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PreCommit_Java_Cron/730/]
> [https://scans.gradle.com/s/6rpbvgwx2nk7c]
> I don't see recent changes, so thinking this is a flake.
> testDefaultRetryPredicate:
> {code:java}
> java.lang.AssertionError
> :
> All incoming requests on node [node_s0] should have finished. Expected 0 but got 2540 Expected: <0L> but: was <2540L>
> at __randomizedtesting.SeedInfo.seed([4CF46FDC92DC07B8:B39A5DDFBC85274E]:0)
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.elasticsearch.test.InternalTestCluster.lambda$assertRequestsFinished$17(InternalTestCluster.java:2086)
> at org.elasticsearch.test.ESTestCase.assertBusy(ESTestCase.java:705)
> at org.elasticsearch.test.ESTestCase.assertBusy(ESTestCase.java:679)
> at org.elasticsearch.test.InternalTestCluster.assertRequestsFinished(InternalTestCluster.java:2083)
> at org.elasticsearch.test.InternalTestCluster.assertAfterTest(InternalTestCluster.java:2062)
> at org.elasticsearch.test.ESIntegTestCase.afterInternal(ESIntegTestCase.java:581)
> at org.elasticsearch.test.ESIntegTestCase.cleanUpCluster(ESIntegTestCase.java:2054)
> ...
> {code}
> This looks like an internal assertion (aka {{checkState}}) failed and the cluster became unhealthy, maybe?
> testWriteRetryValidRequest:
> {code:java}
> org.apache.beam.sdk.Pipeline$PipelineExecutionException
> :
> java.io.IOException: listener timeout after waiting for [90000] ms
> Open stacktrace
> Caused by:
> java.io.IOException
> :
> listener timeout after waiting for [90000] ms
> Close stacktrace
> at org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:899)
> at org.elasticsearch.client.RestClient.performRequest(RestClient.java:227)
> at org.elasticsearch.client.RestClient.performRequest(RestClient.java:321)
> at org.apache.beam.sdk.io.elasticsearch.ElasticsearchIO$Write$WriteFn.flushBatch(ElasticsearchIO.java:1285)
> at org.apache.beam.sdk.io.elasticsearch.ElasticsearchIO$Write$WriteFn.finishBundle(ElasticsearchIO.java:1260){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)