[jira] [Commented] (AMBARI-18827) Allow acceptor / seclector configuration for API and agent connectors

2016-11-16 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18827:
-

ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6030 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6030/])
AMBARI-18827. Allow acceptor / seclector configuration for API and agent 
(swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d92dc0ed47172f69293c1052ef2b7244462bb893])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java


> Allow acceptor / seclector configuration for API and agent connectors
> -
>
> Key: AMBARI-18827
> URL: https://issues.apache.org/jira/browse/AMBARI-18827
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.2.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18827-1.patch, AMBARI-18827.patch
>
>
> _Objectives_:
> - Allow acceptors for agent and api connectors to be configurable
> - The thread pool configuration did not take into account both 2-way and 
> 1-way connectors are configured for agent every time although only one is 
> used and not a mixed-mode. This causes insufficient threads in agent 
> threadpool for a high cpu core environment.



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


[jira] [Commented] (AMBARI-18827) Allow acceptor / seclector configuration for API and agent connectors

2016-11-16 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18827:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #344 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/344/])
AMBARI-18827. Allow acceptor / seclector configuration for API and agent 
(swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43d30212f54f1f3e9b847712a9df8a776a266370])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java


> Allow acceptor / seclector configuration for API and agent connectors
> -
>
> Key: AMBARI-18827
> URL: https://issues.apache.org/jira/browse/AMBARI-18827
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.2.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18827-1.patch, AMBARI-18827.patch
>
>
> _Objectives_:
> - Allow acceptors for agent and api connectors to be configurable
> - The thread pool configuration did not take into account both 2-way and 
> 1-way connectors are configured for agent every time although only one is 
> used and not a mixed-mode. This causes insufficient threads in agent 
> threadpool for a high cpu core environment.



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


[jira] [Commented] (AMBARI-18827) Allow acceptor / seclector configuration for API and agent connectors

2016-11-16 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-18827:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12839219/AMBARI-18827-1.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9302//console

This message is automatically generated.

> Allow acceptor / seclector configuration for API and agent connectors
> -
>
> Key: AMBARI-18827
> URL: https://issues.apache.org/jira/browse/AMBARI-18827
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.2.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18827-1.patch, AMBARI-18827.patch
>
>
> _Objectives_:
> - Allow acceptors for agent and api connectors to be configurable
> - The thread pool configuration did not take into account both 2-way and 
> 1-way connectors are configured for agent every time although only one is 
> used and not a mixed-mode. This causes insufficient threads in agent 
> threadpool for a high cpu core environment.



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


[jira] [Commented] (AMBARI-18827) Allow acceptor / seclector configuration for API and agent connectors

2016-11-14 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18827:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #318 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/318/])
AMBARI-18827. Allow acceptor / seclector configuration for API and agent 
(swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2094dc406dd3ffd2785dc4b39f7e240724531e6a])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/unsecured/rest/ConnectionInfo.java
* (edit) ambari-server/docs/configuration/index.md


> Allow acceptor / seclector configuration for API and agent connectors
> -
>
> Key: AMBARI-18827
> URL: https://issues.apache.org/jira/browse/AMBARI-18827
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.2.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18827.patch
>
>
> _Objectives_:
> - Allow acceptors for agent and api connectors to be configurable
> - The thread pool configuration did not take into account both 2-way and 
> 1-way connectors are configured for agent every time although only one is 
> used and not a mixed-mode. This causes insufficient threads in agent 
> threadpool for a high cpu core environment.



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


[jira] [Commented] (AMBARI-18827) Allow acceptor / seclector configuration for API and agent connectors

2016-11-14 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18827:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6007 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6007/])
AMBARI-18827. Allow acceptor / seclector configuration for API and agent 
(swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4d7d3cdc6380db63bf9b1b221f548cd4470e2a51])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit) ambari-server/docs/configuration/index.md
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/unsecured/rest/ConnectionInfo.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java


> Allow acceptor / seclector configuration for API and agent connectors
> -
>
> Key: AMBARI-18827
> URL: https://issues.apache.org/jira/browse/AMBARI-18827
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.2.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18827.patch
>
>
> _Objectives_:
> - Allow acceptors for agent and api connectors to be configurable
> - The thread pool configuration did not take into account both 2-way and 
> 1-way connectors are configured for agent every time although only one is 
> used and not a mixed-mode. This causes insufficient threads in agent 
> threadpool for a high cpu core environment.



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


[jira] [Commented] (AMBARI-18827) Allow acceptor / seclector configuration for API and agent connectors

2016-11-09 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-18827:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12838235/AMBARI-18827.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 1 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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9206//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9206//console

This message is automatically generated.

> Allow acceptor / seclector configuration for API and agent connectors
> -
>
> Key: AMBARI-18827
> URL: https://issues.apache.org/jira/browse/AMBARI-18827
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.2.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18827.patch
>
>
> _Objectives_:
> - Allow acceptors for agent and api connectors to be configurable
> - The thread pool configuration did not take into account both 2-way and 
> 1-way connectors are configured for agent every time although only one is 
> used and not a mixed-mode. This causes insufficient threads in agent 
> threadpool for a high cpu core environment.



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