You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Selvamohan Neethiraj (JIRA)" <ji...@apache.org> on 2015/06/09 08:30:00 UTC

[jira] [Commented] (RANGER-539) Rolling downgrade changes

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

Selvamohan Neethiraj commented on RANGER-539:
---------------------------------------------

Patch approved and committed - 2c54590a83ab4cf37924876ae468699746d2a751

> Rolling downgrade changes
> -------------------------
>
>                 Key: RANGER-539
>                 URL: https://issues.apache.org/jira/browse/RANGER-539
>             Project: Ranger
>          Issue Type: Bug
>    Affects Versions: 0.5.0
>            Reporter: Velmurugan Periasamy
>            Assignee: Selvamohan Neethiraj
>            Priority: Critical
>         Attachments: 0001-RANGER-539-fixes-to-support-rolling-upgrade-downgrad.patch
>
>
> Need to enable rolling upgrade/downgrade for ranger admin and ranger usersync.
> 1] to support rolling downgrade, disable SHA password until upgrade is finalized
> 2] use bundled log4j to avoid missing config on classpath after upgrade
> 3] enforce minimum sleep time
> 4] Be flexible on ugsync source configuration



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