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

hansonhe commented on YARN-4754:
--------------------------------

[~mr.wang] ,yes ,{color:#2a2b2e}chinese. Ranger just can be able to configure 
yarn access  without to configure about timelineserver. As i konwn yarn on 
ranger just be related to control access  to user queue. 
.And{color}{color:#2a2b2e} my ranger product environment doesn't configure any 
yarn access. I'm sure the users running task have enough permission to access 
such as queue. No any exceptions or errors about permissions  occured on 
rm,nm,timeserver server backgroud logs.{color}

> Too many connection opened to TimelineServer while publishing entities
> ----------------------------------------------------------------------
>
>                 Key: YARN-4754
>                 URL: https://issues.apache.org/jira/browse/YARN-4754
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Rohith Sharma K S
>            Priority: Critical
>         Attachments: ConnectionLeak.rar
>
>
> It is observed that there are too many connections are kept opened to 
> TimelineServer while publishing entities via SystemMetricsPublisher. This 
> cause sometimes resource shortage for other process or RM itself
> {noformat}
> tcp        0      0 10.18.99.110:3999       10.18.214.60:59265      
> ESTABLISHED 115302/java         
> tcp        0      0 10.18.99.110:25001      :::*                    LISTEN    
>   115302/java         
> tcp        0      0 10.18.99.110:25002      :::*                    LISTEN    
>   115302/java         
> tcp        0      0 10.18.99.110:25003      :::*                    LISTEN    
>   115302/java         
> tcp        0      0 10.18.99.110:25004      :::*                    LISTEN    
>   115302/java         
> tcp        0      0 10.18.99.110:25005      :::*                    LISTEN    
>   115302/java         
> tcp        1      0 10.18.99.110:48866      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:48137      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:47553      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:48424      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:48139      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:48096      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:47558      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> tcp        1      0 10.18.99.110:49270      10.18.99.110:8188       
> CLOSE_WAIT  115302/java         
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to