You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/04 14:20:00 UTC
[jira] [Work logged] (BEAM-12815) Flink Go XVR tests fail on TestXLang_Multi: Insufficient number of network buffers
[ https://issues.apache.org/jira/browse/BEAM-12815?focusedWorklogId=752290&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-752290 ]
ASF GitHub Bot logged work on BEAM-12815:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/22 14:19
Start Date: 04/Apr/22 14:19
Worklog Time Spent: 10m
Work Description: asf-ci commented on PR #17263:
URL: https://github.com/apache/beam/pull/17263#issuecomment-1087619124
Can one of the admins verify this patch?
Issue Time Tracking
-------------------
Worklog Id: (was: 752290)
Time Spent: 1h 10m (was: 1h)
> Flink Go XVR tests fail on TestXLang_Multi: Insufficient number of network buffers
> ----------------------------------------------------------------------------------
>
> Key: BEAM-12815
> URL: https://issues.apache.org/jira/browse/BEAM-12815
> Project: Beam
> Issue Type: Bug
> Components: cross-language, sdk-go, test-failures
> Reporter: Daniel Oliveira
> Assignee: Danny McCormick
> Priority: P3
> Fix For: Not applicable
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When running the cross-language test suites () Flink fails on TestXLang_Multi with the following error:
> {noformat}
> 19:29:14 2021/08/27 02:29:14 (): java.io.IOException: Insufficient number of network buffers: required 17, but only 16 available. The total number of network buffers is currently set to 2048 of 32768 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'.
> 19:29:14 2021/08/27 02:29:14 Job state: FAILED
> 19:29:14 --- FAIL: TestXLang_Multi (6.26s){noformat}
> This doesn't seem to be a parallelism problem (go test is run with "-p 1" as expected) and is only happening on this specific test.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)