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

anders updated YARN-2142:
-------------------------

    Description: 
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***

OAT wiki link:
<https://github.com/OpenAttestation/OpenAttestation/wiki>

  was:
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***



> 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: abc.patch, final.patch, final.patch, trust .patch, 
> trust.patch, trust.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***
> OAT wiki link:
> <https://github.com/OpenAttestation/OpenAttestation/wiki>



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to