You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Abhishek Singh (Jira)" <ji...@apache.org> on 2026/09/29 10:25:00 UTC
[jira] [Resolved] (RANGER-5764) Enhancing the performance of RangerUserStore
[ https://issues.apache.org/jira/browse/RANGER-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Singh resolved RANGER-5764.
------------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
> Enhancing the performance of RangerUserStore
> ---------------------------------------------
>
> Key: RANGER-5764
> URL: https://issues.apache.org/jira/browse/RANGER-5764
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Affects Versions: 3.0.0
> Reporter: Abhishek Singh
> Assignee: Abhishek Singh
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently, when RangerUserStoreCache refreshes the user store from the database, it always attempts to load user-to-group mappings. In large deployments with a high number of users and groups, loading these mappings on every refresh can significantly increase DB load time and memory footprint, even when downstream consumers do not require the user-group mappings.
> Therefore a flag based approach can be Proposed to include or exclude the user-group mappings .
> Currently this line in RangerUserStoreCache.java
> final Map<String, Set<String>> userGroups = xUserMgr.getUserGroups() , is the main case of the performance issues in large environments .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)