ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21737) Ambari should expose whether a service is able to rolling-restart instead of hard coding service name
Date Thu, 24 Aug 2017 10:30:00 GMT

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

Hadoop QA commented on AMBARI-21737:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12882283/AMBARI-21737.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12057//console

This message is automatically generated.

> Ambari should expose whether a service is able to rolling-restart instead of hard coding
service name
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21737
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21737
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Madhuvanthi Radhakrishnan
>            Assignee: Madhuvanthi Radhakrishnan
>         Attachments: AMBARI-21737.patch
>
>
> Add a new property rollingRestartSupported to component in the metainfo.xml file. This
property can be used to decide whether the component supports rolling restart.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message