[
https://issues.apache.org/jira/browse/RANGER-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538332#comment-16538332
]
Pradeep Agrawal commented on RANGER-2149:
-----------------------------------------
MySQL-5.6
RAM - 20GB
{code:java}
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Stepping: 1
CPU MHz: 2399.998
BogoMIPS: 4799.99
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0,1
{code}
!bulkpolicytest.png!
--
> REST search queries make Ranger incredibly slow
> ------------------------------------------------
>
> Key: RANGER-2149
> URL: https://issues.apache.org/jira/browse/RANGER-2149
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 0.7.0
> Reporter: Alexander Posledov
> Assignee: Pradeep Agrawal
> Priority: Major
> Attachments: bulkpolicytest.png, totalPolicy.png
>
>
> If amount of Ranger policies is relatively big (3000-4000), then REST search
> queries (e.g. search policy by name) make Ranger very slow. Example:
> curl -u admin:admin -X GET
> http://host:6080/service/plugins/policies?policyName=somePolicyName
> 2-3 such queries (if we have ~3k policies) can cause too long delays even for
> simple requests, while these searches aren't completed. In some cases, when
> we ran several search queries simultaneously, this Ranger behavior caused 9
> min delay for simple adding a new policy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
