ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18205) RU, order Kafka right after Ranger and before HDFS in upgrade pack
Date Thu, 18 Aug 2016 23:15:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-18205:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Pushed to trunk, commit 125be0469998b608d541e00e1e2ae8b05223ab6d
branch-2.4, commit 3643111292af73c7a78f22012f98bb9a0336f9f8

> RU, order Kafka right after Ranger and before HDFS in upgrade pack
> ------------------------------------------------------------------
>
>                 Key: AMBARI-18205
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18205
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.4.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-18205.patch
>
>
> The Rolling Upgrade packs have the wrong order for Kafka since it should be right after
Ranger and before HDFS.
> Kafka is one of the plugins supported by Ranger, so if the plugin is enabled, then during
RU the "get repo call" fails with 25 tries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message