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

kyungwan nam commented on YARN-9386:
------------------------------------

Thank you for your comment!

[~billie.rinaldi]
I agreed with you. I will upload it shortly.

[~wangda]
Yes, only owner or admin can do operations like start/stop/destroy as you said.
It is not about granular permission.

stopped service can be restarted with existing configuration whenever we want.
unlike stop, destroy is irreversible. once destroy is requested, it will delete 
permanently.
when a running service is destroyed by mistake, it is not possible to recover.
that’s the dangerous thing I’m thinking.
so, destroy should be allowed for stopped service only.


> destroying yarn-service is allowed even though running state
> ------------------------------------------------------------
>
>                 Key: YARN-9386
>                 URL: https://issues.apache.org/jira/browse/YARN-9386
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn-native-services
>            Reporter: kyungwan nam
>            Assignee: kyungwan nam
>            Priority: Major
>         Attachments: YARN-9386.001.patch, YARN-9386.002.patch
>
>
> It looks very dangerous to destroy a running app. It should not be allowed.
> {code}
> [yarn-ats@test ~]$ yarn app -list
> 19/03/12 17:48:49 INFO client.RMProxy: Connecting to ResourceManager at 
> test1.com/10.1.1.11:8050
> 19/03/12 17:48:50 INFO client.AHSProxy: Connecting to Application History 
> server at test1.com/10.1.1.101:10200
> Total number of applications (application-types: [], states: [SUBMITTED, 
> ACCEPTED, RUNNING] and tags: []):3
>                 Application-Id      Application-Name        Application-Type  
>         User           Queue                   State             Final-State  
>            Progress                        Tracking-URL
> application_1551250841677_0003                    fb            yarn-service  
>    ambari-qa         default                 RUNNING               UNDEFINED  
>                100%                                 N/A
> application_1552379723611_0002                   fb1            yarn-service  
>     yarn-ats         default                 RUNNING               UNDEFINED  
>                100%                                 N/A
> application_1550801435420_0001             ats-hbase            yarn-service  
>     yarn-ats         default                 RUNNING               UNDEFINED  
>                100%                                 N/A
> [yarn-ats@test ~]$ yarn app -destroy fb1
> 19/03/12 17:49:02 INFO client.RMProxy: Connecting to ResourceManager at 
> test1.com/10.1.1.11:8050
> 19/03/12 17:49:02 INFO client.AHSProxy: Connecting to Application History 
> server at test1.com/10.1.1.101:10200
> 19/03/12 17:49:02 INFO client.RMProxy: Connecting to ResourceManager at 
> test1.com/10.1.1.11:8050
> 19/03/12 17:49:02 INFO client.AHSProxy: Connecting to Application History 
> server at test1.com/10.1.1.101:10200
> 19/03/12 17:49:02 INFO util.log: Logging initialized @1637ms
> 19/03/12 17:49:07 INFO client.ApiServiceClient: Successfully destroyed 
> service fb1
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to