flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4127) Clean up configuration and check breaking API changes
Date Thu, 07 Jul 2016 13:44:11 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366122#comment-15366122

ASF GitHub Bot commented on FLINK-4127:

Github user rmetzger commented on the issue:

    So you are suggesting to use the heap cutoff also for the JVM started in standalone mode?
    The cutoff was introduced for YARN because there is a difference in the amount of used
memory for a container we specify to YARN vs the memory the JVM is actually using.
    So if we specify a container of 1000 MB, it will be killed by YARN as soon as we use 1001
MBs. For operating systems, this doesn't apply and if users run into issues, the can just
set a lower heap size.
    For Mesos, I don't know how it behaves, but I hope that there is a similar requirement,
otherwise, we would have prematurely optimized the configuration keys.
    I'm against applying this mechanism to all JVMs we start.
    For the environment variables of the standalone mode, its quite easy to put the environment
variables into the config.sh file, or just set the env variables.
    But true, we could do a follow up JIRA to extract those env variables and set them in
the config.sh script.

> Clean up configuration and check breaking API changes
> -----------------------------------------------------
>                 Key: FLINK-4127
>                 URL: https://issues.apache.org/jira/browse/FLINK-4127
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>             Fix For: 1.1.0
>         Attachments: flink-core.html, flink-java.html, flink-scala.html, flink-streaming-java.html,
> For the upcoming 1.1. release, I'll check if there are any breaking API changes and if
the documentation is up tp date with the configuration.

This message was sent by Atlassian JIRA

View raw message