You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/08/29 16:34:20 UTC
[jira] [Commented] (AMBARI-18270) Host delete should support a
force option to delete all components
[ https://issues.apache.org/jira/browse/AMBARI-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446365#comment-15446365 ]
Hadoop QA commented on AMBARI-18270:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12825897/AMBARI-18270.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8525//console
This message is automatically generated.
> Host delete should support a force option to delete all components
> ------------------------------------------------------------------
>
> Key: AMBARI-18270
> URL: https://issues.apache.org/jira/browse/AMBARI-18270
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18270.patch
>
>
> AMBARI-15847 added support for bulk host delete but still required deleting components first in each host.
> Thus to make bulk host delete API usable in scenarios where each host may have one or more components, an option should be added to the host delete API to delete all host components if they are in INSTALLED state.
> Sample call:
> {code}
> DELETE http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/hosts
> {"RequestInfo":{"query":"Hosts/host_name.in(c6401.ambari.apache.org,c6402.ambari.apache.org,c6403.ambari.apache.org)", "force_delete_components":"true"}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)