You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/23 16:16:00 UTC

[jira] [Updated] (AMBARI-24291) Start All Services on 100-nodes cluster timed out after 1 hour

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

ASF GitHub Bot updated AMBARI-24291:
------------------------------------
    Labels: pull-request-available  (was: )

> Start All Services on 100-nodes cluster timed out after 1 hour
> --------------------------------------------------------------
>
>                 Key: AMBARI-24291
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24291
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.1
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.1
>
>
> ambari-server with 16 core CPU, 32GB RAM, fake agents on 2 hosts (16GB RAM, 2 core CPU) - 50 agents on each host, Mysql db on last host
>  # Deploy a PERF cluster with 100 fake agents
>  # Initiate Stop All components
>  # Initiate Start All components
> Observations:
>  # As part of initial deploy and start services, the Start All Services call took about 6 minutes.
>  # The first call to Stop All Services took about 23 minutes.
>  # The subsequent call to Start All services timed out after 1 hour 1 minute.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)