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-5726) Adding Oozie failed at service check
Date Sat, 10 May 2014 22:03:45 GMT

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

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

Apart from the fixes described in the description the patch also makes sure that *Add service
wizard* just starts services that are selected in the "Add service wizard" instead of starting
all services in INSTALLED state. Earlier I discovered that if we have stopped services in
the cluster and try to add a new service then along with the new added services other stopped
service are also started by the wizard.

> Adding Oozie failed at service check
> ------------------------------------
>
>                 Key: AMBARI-5726
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5726
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 1.6.0
>
>         Attachments: AMBARI-5726.patch
>
>
> This happens because HDFS and YARN/MapReduce requires to be restarted for Oozie smoke
test to pass successfully
> *As a fix to this issue:*
> # Don't run smoke test on "Install, Start and Test" page of the add service wizard.
> # Review page should ask user to restart all stale services.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message