ashangit opened a new pull request #8760: [FLINK-12869] Add yarn acls 
capability to flink containers
URL: https://github.com/apache/flink/pull/8760
 
 
   ## What is the purpose of the change
   
   *Provide yarn application acls mechanism  on flink containers  to be able to 
provide specific rights to other users than the one running the job (view logs 
through the resourcemanager/job history, kill the application)*
   
   
   ## Brief change log
   
     - *Add 2 parameter (yarn.view.acls and yarn.admin.acls and set 
ApplicationACLs for all containers*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Manually verified the change by running a WordCount job on a yarn 
cluster with acls enabled. Verifying that without yarn.admin.acls a user not 
running the app can't kill the app. Then relaunching the app providing rights 
to an other user (setting yarn.admin.acls) and check that the specified user 
can kill the app. The same can be done for yarn.view.acls by checking that the 
user can now access the application overview from the resourcemanager 
(<resourcemanager_url>/cluster/app/<app_id>)*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: Affect acls on YARN 
(currently not managed so no rights can be added)
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? docs

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to