flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-1427) Configuration through environment variables
Date Tue, 19 Apr 2016 11:55:25 GMT

     [ https://issues.apache.org/jira/browse/FLINK-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Maximilian Michels closed FLINK-1427.
    Resolution: Won't Fix

Thanks, closing for now.

> Configuration through environment variables
> -------------------------------------------
>                 Key: FLINK-1427
>                 URL: https://issues.apache.org/jira/browse/FLINK-1427
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>         Environment: Deployment
>            Reporter: Maximilian Michels
>            Priority: Minor
>              Labels: configuration, deployment
> Like Hadoop or Spark, etc. Flink should support configuration via shell environment variables.
In cluster setups, this makes things a lot easier because writing config files can be omitted.
Many automation tools (e.g. Google's bdutil) use (or abuse) this feature.
> For example, to set up the task manager heap size, we would run `export FLINK_TASKMANAGER_HEAP=4096`
before starting the task manager on a node to set the heap memory size to 4096MB.
> Environment variables should overwrite the regular config entries.

This message was sent by Atlassian JIRA

View raw message