Anand Srinivasan created YARN-10068:
---------------------------------------
Summary: TimelineV2Client may leak file descriptors creating
ClientResponse objects.
Key: YARN-10068
URL: https://issues.apache.org/jira/browse/YARN-10068
Project: Hadoop YARN
Issue Type: Bug
Components: ATSv2
Affects Versions: 3.0.0
Environment: HDP VERSION3.1.4
AMBARI VERSION2.7.4.0
Reporter: Anand Srinivasan
Hi team,
Code-walkthrough between v1 and v2 of TimelineClient API revealed that v2 API
TimelineV2ClientImpl#putObjects doesn't close ClientResponse objects under
success status returned from Timeline Server. ClientResponse is closed only
under erroneous response from the server using ClientResponse#getEntity.
We also noticed that TimelineClient (v1) closes the ClientResponse object in
TimelineWriter#putEntities by calling ClientResponse#getEntity in both success
and error conditions from the server thereby avoiding this file descriptor leak.
Customer's original issue and the symptom was that the NodeManager went down
because of 'too many files open' condition where there were lots of CLOSED_WAIT
sockets observed between the timeline client (from NM) and the timeline server
hosts.
Could you please help resolve this issue ? Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
