You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/05/12 07:57:00 UTC

[jira] [Created] (FLINK-27578) Elasticsearch6SinkE2ECase.testScaleUp fails after "Exhausted retry attempts"

Martijn Visser created FLINK-27578:
--------------------------------------

             Summary: Elasticsearch6SinkE2ECase.testScaleUp fails after "Exhausted retry attempts"
                 Key: FLINK-27578
                 URL: https://issues.apache.org/jira/browse/FLINK-27578
             Project: Flink
          Issue Type: Bug
          Components: Connectors / ElasticSearch
            Reporter: Martijn Visser


https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=35588&view=logs&j=af184cdd-c6d8-5084-0b69-7e9c67b35f7a&t=160c9ae5-96fd-516e-1c91-deb81f59292a&l=117547


{code:java}
--------------------------------------------------------------------------------
Test org.apache.flink.streaming.tests.Elasticsearch6SinkE2ECase.testScaleUp failed with:
org.apache.flink.util.FlinkException: Exhausted retry attempts.
	at org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:173)
	at org.apache.flink.streaming.tests.ElasticsearchSinkE2ECaseBase.checkResultWithSemantic(ElasticsearchSinkE2ECaseBase.java:76)
	at org.apache.flink.connector.testframe.testsuites.SinkTestSuiteBase.restartFromSavepoint(SinkTestSuiteBase.java:326)
	at org.apache.flink.connector.testframe.testsuites.SinkTestSuiteBase.testScaleUp(SinkTestSuiteBase.java:201)
{code}

These test runs are also flooding the logs (see above), which causes all E2E tests to fail due to running out of disk space on the Azure provided machines. See https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=35599&view=logs&s=ae4f8708-9994-57d3-c2d7-b892156e7812&j=af184cdd-c6d8-5084-0b69-7e9c67b35f7a or https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=35573&view=logs&s=ae4f8708-9994-57d3-c2d7-b892156e7812&j=af184cdd-c6d8-5084-0b69-7e9c67b35f7a for example. 

This issue most likely causes FLINK-24433



--
This message was sent by Atlassian Jira
(v8.20.7#820007)