Sergey Nuyanzin created FLINK-35094:
---------------------------------------
Summary: SinkTestSuiteBase.testScaleDown is hanging for
1.20-SNAPSHOT
Key: FLINK-35094
URL: https://issues.apache.org/jira/browse/FLINK-35094
Project: Flink
Issue Type: Bug
Components: Connectors / ElasticSearch
Affects Versions: elasticsearch-3.1.0, 1.20.0
Reporter: Sergey Nuyanzin
Currently it is reproduced for elastic search connector
all the ci jobs (for all jdks) against 1.20-SNAPSHOT are hanging on
{noformat}
2024-04-12T05:56:50.6179284Z "main" #1 prio=5 os_prio=0 cpu=18726.96ms
elapsed=2522.03s tid=0x00007f670c025a50 nid=0x3c6d waiting on condition
[0x00007f6712513000]
2024-04-12T05:56:50.6180667Z java.lang.Thread.State: TIMED_WAITING (sleeping)
2024-04-12T05:56:50.6181497Z at
java.lang.Thread.sleep(java.base@17.0.10/Native Method)
2024-04-12T05:56:50.6182762Z at
org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:152)
2024-04-12T05:56:50.6184456Z at
org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:145)
2024-04-12T05:56:50.6186346Z at
org.apache.flink.connector.testframe.testsuites.SinkTestSuiteBase.checkResultWithSemantic(SinkTestSuiteBase.java:504)
2024-04-12T05:56:50.6188474Z at
org.apache.flink.connector.testframe.testsuites.SinkTestSuiteBase.restartFromSavepoint(SinkTestSuiteBase.java:327)
2024-04-12T05:56:50.6190145Z at
org.apache.flink.connector.testframe.testsuites.SinkTestSuiteBase.testScaleDown(SinkTestSuiteBase.java:224)
2024-04-12T05:56:50.6191247Z at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@17.0.10/Native
Method)
2024-04-12T05:56:50.6192806Z at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@17.0.10/NativeMethodAccessorImpl.java:77)
2024-04-12T05:56:50.6193863Z at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@17.0.10/DelegatingMethodAccessorImpl.java:43)
2024-04-12T05:56:50.6194834Z at
java.lang.reflect.Method.invoke(java.base@17.0.10/Method.java:568)
{noformat}
for 1.17, 1.18, 1.19 there is no such issue and everything is ok
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
