K0K0V0K opened a new pull request, #8378:
URL: https://github.com/apache/hadoop/pull/8378

   
   ### Description of PR
   
   The goal of this feature tp provide a configurable mechanism to control 
which users are allowed to execute specific MapReduce jobs. This feature aims 
to prevent unauthorized or potentially harmful mapper/reducer implementations 
from running within the Hadoop cluster.
   
   In the standard Hadoop MapReduce execution flow:
   1) A MapReduce job is submitted by a user.
   2) The job is registered with the Resource Manager (RM). 
   3) The RM assigns the job to a Node Manager (NM), where the Application 
Master (AM) for the job is launched. 
   4) The AM requests additional containers from the cluster, to be able to 
start tasks. 
   5) The NM launches those containers, and the containers execute the 
mapper/reducer tasks defined by the job.
   
   The proposed feature introduces a security filtering mechanism inside the 
Application Master. Before mapper or reducer tasks are launched, the AM will 
verify that the user-submitted MapReduce code complies with a cluster-defined 
security policy. This ensures that only approved classes or packages can be 
executed inside the containers. The goal is to protect the cluster from 
unwanted or unsafe task implementations, such as custom code that may introduce 
performance, stability, or security risks.
   
   Upon receiving job metadata, the Application Master will: 
   1) Check the feature is enabled.
   2) Check the user who submitted the job is allowed to bypass the security 
check. 
   3) Compare classes in job config against the denied task list. 
   4) If job is not authorised an exception will be thrown and AM will fail.
   
   ### How was this patch tested?
   
   UT was created
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   ### AI Tooling
   
   If an AI tool was used:
   
   - [ ] The PR includes the phrase "Contains content generated by <tool>"
         where <tool> is the name of the AI tool used.
   - [ ] My use of AI contributions follows the ASF legal policy
         https://www.apache.org/legal/generative-tooling.html


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to