You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2017/02/14 20:34:41 UTC

[jira] [Resolved] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs

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

Vitaly Brodetskyi resolved AMBARI-19058.
----------------------------------------
    Resolution: Fixed

Committed to trunk and branch-2.5

> Perf: Deploy 3000 Agent cluster and find perf bugs
> --------------------------------------------------
>
>                 Key: AMBARI-19058
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19058
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19058_part1.patch, AMBARI-19058_part2.patch, AMBARI-19058_part3.patch, AMBARI-19058_part4.patch, AMBARI-19058_part5.patch
>
>
> Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and start finding perf bugs in the following areas.
> Agent registration (batches of 600 at a time are still very slow)
> Alerts
> Commands like starting/restarting/rolling restart, etc.
> Memory leaks after letting it run for a week?
> We may need to also run a memory profiler on the java process.



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