You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2016/11/28 21:51:58 UTC

[jira] [Updated] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings

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

Alejandro Fernandez updated AMBARI-19003:
-----------------------------------------
    Description: 
Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core VM where it puts 50 agents. Instead, we need to create a separate 16-core VM for the server without any agents.
Next, Ambari Server should be installed with MySQL database instead since it has more configuration options that the default postgres.

Further, the sorting of the VMs is not numeric since "perf-9" comes after "perf-42". The incorrect sorting means that VM #i isn't getting the agents starting with number (i-1)*50+1

  was:
Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core VM where it puts 50 agents. Instead, we need to create a separate 16-core VM for the server without any agents.

Further, the sorting of the VMs is not numeric since "perf-9" comes after "perf-42". The incorrect sorting means that VM #i isn't getting the agents starting with number (i-1)*50+1


> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19003
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19003
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.5.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.5.0
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core VM where it puts 50 agents. Instead, we need to create a separate 16-core VM for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after "perf-42". The incorrect sorting means that VM #i isn't getting the agents starting with number (i-1)*50+1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)