Ayub Pathan created KNOX-1011:
---------------------------------
Summary: Knox LDAP demo server port(33389) is hardcoded. provide
an option to make it configurable.
Key: KNOX-1011
URL: https://issues.apache.org/jira/browse/KNOX-1011
Project: Apache Knox
Issue Type: Bug
Components: KnoxSSO
Affects Versions: 0.12.0
Reporter: Ayub Pathan
Priority: Critical
[[Background]]
h2. *Problem:* Knox demo LDAP server fails to start intermittently(happening
more frequently these days), resulting in knox tests failures. LDAP server
fails to start because port 33389, which it uses for listening incoming
connections is already occupied on the machine.
h2. *RCA:*
*Question: why are we seeing zookeeper node using 33389 port?*
* ZooKeeper has the notion of ephemeral nodes. These ephemeral znodes exists as
long as the session that created the znode is active. When the session ends the
znode is deleted. These ephemeral nodes make use of ephemeral ports depending
on the system configuration.
This ephemeral port is taken from the range defined by the output of the
following command.
{noformat}
[root@ctr-e134-1499953498516-111711-01-000004 ~]# sysctl
net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 32768 61000
[root@ctr-e134-1499953498516-111711-01-000004 ~]#
{noformat}
*These ephemeral znodes exists as long as the session that created the znode is
active*. This is the reason we are seeing zookeeper nodes using 33389 port
randomly sometimes, which is resulting in LDAP server startup failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
