ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2079) Can't change service configuration if heartbeat lost from service component host
Date Sat, 04 May 2013 01:15:13 GMT

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

Jaimin D Jetly commented on AMBARI-2079:
----------------------------------------

+1 for the patch.
                
> Can't change service configuration if heartbeat lost from service component host
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-2079
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2079
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.3.0
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>            Priority: Critical
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-2079.patch
>
>
> Currently, the UI blocks the user from saving configurations unless all components belonging
to the service are in INSTALLED state.
> Since there's no "remove host" capability, if you have hosts that are down in the cluster,
this means that the user can never make config changes, as the components on the downed hosts
will be in UNKNOWN state.
> Therefore, we should allow the user to proceed with config save as long as all the service
components are in INSTALLED OR UNKNOWN state. In case there are some components in UNKNOWN
state, we should just warn the user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message