[
https://issues.apache.org/jira/browse/BEAM-12753?focusedWorklogId=739663&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-739663
]
ASF GitHub Bot logged work on BEAM-12753:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Mar/22 18:33
Start Date: 10/Mar/22 18:33
Worklog Time Spent: 10m
Work Description: damccorm opened a new pull request #17067:
URL: https://github.com/apache/beam/pull/17067
**Please** add a meaningful description for your change here
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [ ] [**Choose
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and
mention them in a comment (`R: @username`).
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue, if applicable. This will automatically link the pull request to the
issue.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 739663)
Time Spent: 50m (was: 40m)
> Flink Runner fails with memory issue when creating first TestStream instance
> ----------------------------------------------------------------------------
>
> Key: BEAM-12753
> URL: https://issues.apache.org/jira/browse/BEAM-12753
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, sdk-go
> Reporter: Jack McCluskey
> Priority: P3
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Running Go SDK TestStream integration tests on the Flink runner consistently
> results in the following error on the first test run regardless of the test
> itself:
>
> {code:java}
> 2021/08/11 21:12:47 (): java.io.IOException: Insufficient number of network
> buffers: required 17, but only 14 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'.
> {code}
> This error is thrown on the first test run on a fresh instance of the Flink
> job server; subsequent test runs of the same suite pass. Stopping the job
> server and starting a new one results in the first test run failing again.
> The memory error is thrown for int64, float64, and boolean data types;
> however, if the first TestStream contains strings or byte slices the memory
> error does not occur. It should be noted that strings and byte slices are
> getting appended with an extra length prefix on the Flink side, although it
> is unclear if that is related.
>
> On further investigation, the bug appears to be environment-specific, with
> many machines unable to reproduce the issue; however, the error still occurs
> on Jenkins for test runs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
