You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "peng.jianhua (JIRA)" <ji...@apache.org> on 2017/05/10 07:26:04 UTC

[jira] [Updated] (RANGER-1569) All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all once it happens.

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

peng.jianhua updated RANGER-1569:
---------------------------------
    Summary: All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all once it happens.  (was: All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all Once it happens.)

> All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all once it happens.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1569
>                 URL: https://issues.apache.org/jira/browse/RANGER-1569
>             Project: Ranger
>          Issue Type: New Feature
>          Components: Ranger
>    Affects Versions: 1.0.0
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>              Labels: newbie
>
> Ranger is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform. All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all once it happens.
> We should provide high availability to solve this problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)