[
https://issues.apache.org/jira/browse/AMBARI-23792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467822#comment-16467822
]
Hudson commented on AMBARI-23792:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9208 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9208/])
AMBARI-23792. Need Ranger Tagsync component to be started at end during
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=653f32a7f0d44f34ffc250db90de4702ac81d60a])
* (edit) ambari-web/app/controllers/main/admin/federation/step4_controller.js
* (edit) ambari-web/app/messages.js
> Need Ranger Tagsync component to be started at end during restart all
> services task for Federation wizard
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-23792
> URL: https://issues.apache.org/jira/browse/AMBARI-23792
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.7.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Current implementation on Federation wizard start Ranger Tagsync before
> Namenode start during start task of Ranger Service. Need Ranger Tagsync
> component to be stopped when we are updating service name in restart of
> namenode.
> So following sequence of starting services needs to be considered.
> # Stop Tagsync (as part of stop all services)
> # Start Ranger Admin and Ranger Usersync
> # Start Namenode
> # Start Ranger Tagsync
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
