[
https://issues.apache.org/jira/browse/FLINK-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341727#comment-15341727
]
Ufuk Celebi commented on FLINK-4039:
------------------------------------
I agree that this is kind of weird, but I think the current behaviour is the
only safe way with respect to not overwriting custom GC settings. We could set
our GC first and hope that the JVM evaluates the arguments in the expected
order, but that's not safe. So I think we can't do anything about this. Do you
have another idea?
> G1 garbage collector only set if no custom jvm arguments
> --------------------------------------------------------
>
> Key: FLINK-4039
> URL: https://issues.apache.org/jira/browse/FLINK-4039
> Project: Flink
> Issue Type: Bug
> Components: Startup Shell Scripts
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Gyula Fora
> Priority: Critical
> Fix For: 1.1.0
>
>
> This can lead to very unexpected behaviour with java 8.
> Let's say I want to profile my job so I set some jvm arguments, but this also
> implicitly change the gc which is kind of weird.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
