[
https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627483#comment-15627483
]
Hadoop QA commented on AMBARI-18733:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836457/AMBARI-18733.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{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/9088//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9088//console
This message is automatically generated.
> Perf: Allow running multiple Ambari Agents on the same host
> -----------------------------------------------------------
>
> Key: AMBARI-18733
> URL: https://issues.apache.org/jira/browse/AMBARI-18733
> Project: Ambari
> Issue Type: Story
> Components: ambari-agent
> Affects Versions: 2.5.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18733.patch
>
>
> Currently there are limitations to running multiple Ambari Agents on the same
> host because it uses a single path for
> /etc/ambari-agent/conf/ambari-agent.ini
> /var/run/ambari-agent/ambari-agent.pid
> /var/lib/ambari-agent/data
> /var/log/ambari-agent/
> Ambari Agent already has a way to change the port, log dir, and pid dir
> through its config file, so we also need it to support its own unique home
> directory with its own unique config file.
> Furthermore, the agent will have to override its hostname.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
