[
https://issues.apache.org/jira/browse/BEAM-6698?focusedWorklogId=201699&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-201699
]
ASF GitHub Bot logged work on BEAM-6698:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Feb/19 00:30
Start Date: 21/Feb/19 00:30
Worklog Time Spent: 10m
Work Description: adude3141 commented on issue #7877: [BEAM-6698]
increase maxHeapSize to prevent OutOfMemoryError (direct …
URL: https://github.com/apache/beam/pull/7877#issuecomment-465812378
@mxm Could you help merging? I forgot to change title when asking for review.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 201699)
Time Spent: 3h 40m (was: 3.5h)
> Portable Validates Runner Tests on Flink flaky after update to gradle5
> -----------------------------------------------------------------------
>
> Key: BEAM-6698
> URL: https://issues.apache.org/jira/browse/BEAM-6698
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Michael Luckey
> Assignee: Michael Luckey
> Priority: Major
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> After upgrade to gradle 5 [1], the two portable runner test projects on
> jenkins
> - beam_PostCommit_Java_PVR_Flink_Streaming [2]
> - beam_PostCommit_Java_PVR_Flink_Batch [3]
> became flaky.
> First investigation seems to point the tests to be failing on direct buffer
> memory (e.g. [4]) while staging files.
> Although I am unsure, whether this is really the root cause, or something
> that shows up after some other failure.
> {noformat}
> INFO: Transport failed
> org.apache.beam.vendor.grpc.v1p13p1.io.netty.util.internal.OutOfDirectMemoryError:
> failed to allocate 16777216 byte(s) of direct memory (used: 1895825695, max:
> 1908932608)
> {noformat}
> As far as I know, we do not set `-XX:MaxDirectMemorySize` anywhere in our
> setup, neither does gradle itself. At least on my machine both gradle 4 and
> gradle 5 stick to the same jvm default
> {noformat}
> ###########################################
> sun.misc.VM.maxDirectMemory(): 1908932608 Bytes
> sun.misc.VM.maxDirectMemory(): 1820 MB
> ###########################################
> {noformat}
>
> Unfortunately this does not reproduce on (my) local machine. We might try to
> workaround here by increasing ` -XX:MaxDirectMemorySize==3G` but this would
> probably only hide the problem? But might still be helpful to increase
> temporarily on branch just to be sure, that this is indeed the root cause?
> [1] https://issues.apache.org/jira/browse/BEAM-6630
> [2] [https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming/]
> [3] [https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/]
> [4]
> [https://scans.gradle.com/s/tpo3yffjznfxa/tests/yobvrae4rwsg4-go44ti5iq45vq]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
