[
https://issues.apache.org/jira/browse/AMBARI-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704312#comment-15704312
]
Hadoop QA commented on AMBARI-19003:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840729/AMBARI-19003.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9425//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9425//console
This message is automatically generated.
> 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)
