[ 
https://issues.apache.org/jira/browse/YARN-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656082#comment-16656082
 ] 

Hudson commented on YARN-8618:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15262 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15262/])
YARN-8618. Added detection for non-upgradable service.            (eyang: rev 
66f059ed1db93c0a86e86c64636013001169a677)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/client/ServiceClient.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/test/java/org/apache/hadoop/yarn/service/client/TestServiceClient.java


> Yarn Service: When all the components of a service have restart policy NEVER 
> then initiation of service upgrade should fail 
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-8618
>                 URL: https://issues.apache.org/jira/browse/YARN-8618
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>            Priority: Major
>             Fix For: 3.2.0, 3.3.0
>
>         Attachments: YARN-8618.001.patch
>
>
> * If all the components are NEVER, we can error out at the service level 
> upgrade command itself and say upgrade not allowed. Otherwise for any other 
> permutation/combination we should accept the service-level upgrade call and 
> mark components which can be upgraded.



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

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

Reply via email to