ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB
Date Tue, 29 Nov 2016 22:30:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706751#comment-15706751
] 

Hudson commented on AMBARI-19003:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #406 (See [https://builds.apache.org/job/Ambari-branch-2.5/406/])
AMBARI-19003. Perf: Fix deploy-gce-perf-cluster.py to deploy separate (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=052da577bcf5c3130337b7e783bda2b9c0207127])
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py


> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with
different settings for more cores and MySQL DB
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 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
>
>         Attachments: AMBARI-19003.patch
>
>
> 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)

Mime
View raw message