You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/01/26 12:02:00 UTC
[jira] [Commented] (FLINK-25819) NetworkBufferPoolTest.testIsAvailableOrNotAfterRequestAndRecycleMultiSegments fails on AZP
[ https://issues.apache.org/jira/browse/FLINK-25819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482418#comment-17482418 ]
Chesnay Schepler commented on FLINK-25819:
------------------------------------------
When I run this locally the thread requesting buffers crashes an IOException:
{code}
Insufficient number of network buffers: required 5, but only 0 available. The total number of network buffers is currently set to 10 of 128 bytes each. You can increase this number by setting the configuration keys 'taskmanager.memory.network.fraction', 'taskmanager.memory.network.min', and 'taskmanager.memory.network.max'.
{code}
As such it appears as if {{globalPool.requestUnpooledMemorySegments}} isn't blocking at all.
> NetworkBufferPoolTest.testIsAvailableOrNotAfterRequestAndRecycleMultiSegments fails on AZP
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-25819
> URL: https://issues.apache.org/jira/browse/FLINK-25819
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Network
> Affects Versions: 1.14.3
> Reporter: Till Rohrmann
> Priority: Critical
> Labels: test-stability
>
> The {{NetworkBufferPoolTest.testIsAvailableOrNotAfterRequestAndRecycleMultiSegments}} fails on AZP with:
> {code}
> Jan 26 07:57:03 [ERROR] testIsAvailableOrNotAfterRequestAndRecycleMultiSegments Time elapsed: 10.028 s <<< ERROR!
> Jan 26 07:57:03 org.junit.runners.model.TestTimedOutException: test timed out after 10 seconds
> Jan 26 07:57:03 at sun.misc.Unsafe.park(Native Method)
> Jan 26 07:57:03 at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> Jan 26 07:57:03 at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:426)
> Jan 26 07:57:03 at java.util.concurrent.FutureTask.get(FutureTask.java:204)
> Jan 26 07:57:03 at org.junit.internal.runners.statements.FailOnTimeout.getResult(FailOnTimeout.java:167)
> Jan 26 07:57:03 at org.junit.internal.runners.statements.FailOnTimeout.evaluate(FailOnTimeout.java:128)
> Jan 26 07:57:03 at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:258)
> Jan 26 07:57:03 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
> Jan 26 07:57:03 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
> Jan 26 07:57:03 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> Jan 26 07:57:03 at java.lang.Thread.run(Thread.java:748)
> {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=30187&view=logs&j=4d4a0d10-fca2-5507-8eed-c07f0bdf4887&t=7b25afdf-cc6c-566f-5459-359dc2585798&l=7350
--
This message was sent by Atlassian Jira
(v8.20.1#820001)