You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/11/16 18:42:58 UTC
[jira] [Reopened] (AMBARI-18827) Allow acceptor / seclector
configuration for API and agent connectors
[ https://issues.apache.org/jira/browse/AMBARI-18827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nahappan Somasundaram reopened AMBARI-18827:
--------------------------------------------
ambari-agent fails to register with the server:
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 167, in registerWithServer
ret = self.sendRequest(self.registerUrl, data)
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 514, in sendRequest
raise IOError('Request to {0} failed due to {1}'.format(url, str(exception)))
IOError: Request to https://localhost:8441/agent/v1/register/c6402.ambari.apache.org failed due to [Errno 111] Connection refused
> 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)