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

Till Rohrmann resolved FLINK-11126.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.1
                   1.9.0
                   1.7.3

Fixed
1.9.0: dac36482e2bc7b16d0c1e8dc8ae986d5cf6c1db6
1.8.1: d044789f202d2ec260056c1dc94cd1dd08ed0b77
1.7.3: 0569fcb1d6f23ee083db686aa9db78f5a210282e

> Filter out AMRMToken in the TaskManager credentials
> ---------------------------------------------------
>
>                 Key: FLINK-11126
>                 URL: https://issues.apache.org/jira/browse/FLINK-11126
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>    Affects Versions: 1.6.2, 1.6.4, 1.7.0, 1.7.2, 1.8.0
>            Reporter: Paul Lin
>            Assignee: Paul Lin
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.7.3, 1.9.0, 1.8.1
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, Flink JobManager propagates its storage tokens to TaskManager to 
> meet the requirement of YARN log aggregation (see FLINK-6376). But in this 
> way the AMRMToken is also included in the TaskManager credentials, which 
> could be potentially insecure. We should filter out AMRMToken before setting 
> the tokens to TaskManager's container launch context.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to