[ 
https://issues.apache.org/jira/browse/KNOX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189490#comment-14189490
 ] 

Josh Ritter commented on KNOX-459:
----------------------------------

This is a kerberized cluster, using Centrify and Active Directory to 
enable/manage kerberos. Discovered this while implementing/testing knox on my 
cluster. Using the following command to test knox configuration:

curl -iku <USER>:<PASSWD> -X GET 
'https://<server.domain.net>:8443/gateway/<cluster_name>/webhdfs/v1?op=LISTSTATUS'
 

Had to increase default ulimit from 1k to 64k just to get knox to function. 
After increasing to 64k knox would run and the above curl command would work. 
Then discovered the long list of orphaned sockets. Wish I had the expertise to 
provide a patch, but am unable to do that at this time.

> Apache knox appears to be leaking sockets
> -----------------------------------------
>
>                 Key: KNOX-459
>                 URL: https://issues.apache.org/jira/browse/KNOX-459
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Release, Server
>    Affects Versions: 0.4.0
>         Environment: RHEL 6.4 on IBM x3650 hardware. Running Hortonworks HDP 
> 2.1.3 product.
>            Reporter: Josh Ritter
>
> Sockets are left open each time a call to rest api is initiated. Tried 
> updating timeout value in config, no affect.
> [root@hdptestsrv01 knox]# ps -ef|grep knox 
> root 9310 6431 0 14:42 pts/0 00:00:00 su - knox 
> knox 9311 9310 0 14:42 pts/0 00:00:00 -bash 
> knox 13813 1 1 14:46 pts/0 00:00:30 /usr/java/latest/bin/java -Xmx4G -jar 
> /usr/lib/knox/bin/gateway.jar 
> root 20252 6499 0 15:11 pts/1 00:00:00 grep knox 
> [root@hdptestsrv01 knox]# lsof -p 13813|grep "sock"|wc -l 
> 2290 
> [root@hdptestsrv01 knox]# lsof -p 13813|grep "sock" 
> java 13813 knox 149u sock 0,6 0t0 52410 can't identify protocol 
> java 13813 knox 150u sock 0,6 0t0 52411 can't identify protocol 
> java 13813 knox 151u sock 0,6 0t0 52412 can't identify protocol 
> java 13813 knox 152u sock 0,6 0t0 52413 can't identify protocol 
> java 13813 knox 153u sock 0,6 0t0 52414 can't identify protocol 
> java 13813 knox 154u sock 0,6 0t0 52415 can't identify protocol 
> java 13813 knox 155u sock 0,6 0t0 52416 can't identify protocol



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

Reply via email to