Vinod Kumar Vavilapalli commented on YARN-2142:

bq. In the cluster ,every node has been registered on one machine which is OAT 
bq. If the node's info(maybe BIOS info ,system info etc) was edited,and the 
current info is not equal to register info ,we can call this nodes is not TRUST 
Can you please reply to my question on what a OAT server is? May be some 

It's very hard to understand what this patch is doing, what its design is and 
why it should be done this way inside YARN. Please post a requirements + design 
doc so the rest of us can understand your intentions. Thanks.

> Add one service to check the nodes' TRUST status 
> -------------------------------------------------
>                 Key: YARN-2142
>                 URL: https://issues.apache.org/jira/browse/YARN-2142
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager, resourcemanager, scheduler, webapp
>         Environment: OS:Ubuntu 13.04; 
> JAVA:OpenJDK 7u51-2.4.4-0
> Only in branch-2.2.0.
>            Reporter: anders
>            Priority: Minor
>              Labels: features
>         Attachments: trust .patch, trust.patch, trust.patch, trust.patch, 
> trust001.patch, trust002.patch, trust003.patch, trust2.patch
>   Original Estimate: 1m
>  Remaining Estimate: 1m
> Because of critical computing environment ,we must test every node's TRUST 
> status in the cluster (We can get the TRUST status by the API of OAT 
> sever),So I add this feature into hadoop's schedule .
> By the TRUST check service ,node can get the TRUST status of itself,
> then through the heartbeat ,send the TRUST status to resource manager for 
> scheduling.
> In the scheduling step,if the node's TRUST status is 'false', it will be 
> abandoned until it's TRUST status turn to 'true'.
> ***The logic of this feature is similar to node's health checkservice.
> ***Only in branch-2.2.0 , not in trunk***

This message was sent by Atlassian JIRA

Reply via email to