ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myroslav Papirkovskyi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-18976) Config History request execution time depends on config versions count
Date Mon, 28 Nov 2016 16:43:58 GMT

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

Myroslav Papirkovskyi resolved AMBARI-18976.
--------------------------------------------
    Resolution: Fixed

Pushed to trunk and branch-2.5

> 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
>
>         Attachments: AMBARI-18976.patch
>
>
> 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)

Mime
View raw message