Github user mxm commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1741#discussion_r57295865
  
    --- Diff: 
flink-core/src/main/java/org/apache/flink/configuration/ConfigConstants.java ---
    @@ -240,6 +246,37 @@
         */
        public static final String FS_STREAM_OPENING_TIMEOUT_KEY = 
"taskmanager.runtime.fs_timeout";
     
    +   
    +   // -------- Common Resource Framework Configuration (YARN & Mesos) 
--------
    +
    +   /**
    +    * Percentage of heap space to remove from containers (YARN / Mesos), 
to compensate
    +    * for other JVM memory usage.
    +    */
    +   public static final String CONTAINERED_HEAP_CUTOFF_RATIO = 
"containered.heap-cutoff-ratio";
    +
    +   /**
    +    * Minimum amount of heap memory to remove in containers, as a safety 
margin.
    +    */
    +   public static final String CONTAINERED_HEAP_CUTOFF_MIN = 
"containered.heap-cutoff-min";
    +
    +   /**
    +    * Prefix for passing custom environment variables to Flink's master 
process.
    +    * For example for passing LD_LIBRARY_PATH as an env variable to the 
AppMaster, set:
    +    * yarn.application-master.env.LD_LIBRARY_PATH: "/usr/lib/native"
    +    * in the flink-conf.yaml.
    +    */
    +   public static final String CONTAINERED_MASTER_ENV_PREFIX = 
"containered.application-master.env.";
    +
    +   /**
    +    * Similar to the {@see CONTAINERED_MASTER_ENV_PREFIX}, this 
configuration prefix allows
    +    * setting custom environment variables for the workers (TaskManagers)
    +    */
    +   public static final String CONTAINERED_TASK_MANAGER_ENV_PREFIX = 
"containered.taskmanager.env.";
    --- End diff --
    
    I thought about theses prefixes again. I think they make sense but we could 
possibly change them before the release in a follow-up.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to