You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Myroslav Papirkovskyi (JIRA)" <ji...@apache.org> on 2016/11/23 16:59:59 UTC
[jira] [Created] (AMBARI-18976) Config History request execution
time depends on config versions count
Myroslav Papirkovskyi created AMBARI-18976:
----------------------------------------------
Summary: Config History request execution time depends on config versions count
Key: AMBARI-18976
URL: https://issues.apache.org/jira/browse/AMBARI-18976
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Priority: Critical
Fix For: 2.5.0
Request: {{/api/v1/clusters/tdk/configurations/service_config_versions?fields=group_id,user&minimal_response=true&from=0&page_size=10}}
Response always contains 10 records or less (if there are less than 10 service configs versions). Each record has only two fields ({{group_id}}, {{user}}).
Request execution time depends on overall count of service config versions in the DB.
Example:
|| Items Total in the DB || Response Time ||
|2 |~140 ms|
|100 |900+ ms|
|290 |3+ s|
|750 |9+ s|
|1000 |15+ s|
|3000 |30+ s|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)