[
https://issues.apache.org/jira/browse/SLIDER-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163313#comment-15163313
]
Steve Loughran commented on SLIDER-1087:
----------------------------------------
I guess destroy comes from the time when start/stop were freeze/thaw (still in
the code if you look)
I'm -1 to having destroy do a stop + delete; having two separate options was
designed to make losing all your data harder. Get "destroy" in when you didn't
mean to, and there goes your HBase dataset. As it is, destroy refuses to work
if your cluster is running, and makes you use the --force option to show that
you really meant it.
We could make "delete" a synonym for destroy...
> Slider client command "destroy" should stop and delete the app
> --------------------------------------------------------------
>
> Key: SLIDER-1087
> URL: https://issues.apache.org/jira/browse/SLIDER-1087
> Project: Slider
> Issue Type: Bug
> Components: client
> Affects Versions: Slider 0.81, Slider 0.90.2
> Reporter: shanyu zhao
>
> Currently these are some Slider client commands:
> - build: build app definitions in HDFS
> - start: start yarn app
> - stop: stop yarn app
> - destroy: delete app definitions from HDFS
> - create: build+start
> The "destroy" command is confusing, if the app is running, you have to "stop"
> it before "destroy" it. Note that the antonym of "create" is "destroy".
> I propose we replace command "destroy" with "delete", and use "destroy" to
> stop and delete app.
> - delete: delete app definitions from HDFS
> - destroy: stop + delete
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
