You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gobblin.apache.org by "Zihan Li (Jira)" <ji...@apache.org> on 2022/02/28 22:26:00 UTC

[jira] [Updated] (GOBBLIN-1616) Make RestliAPIConnector be able to close the connection finally

     [ https://issues.apache.org/jira/browse/GOBBLIN-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zihan Li updated GOBBLIN-1616:
------------------------------
    Description: In RestApiConnector, we only consume the HttpEntity but not close the response, which potentially leave the socket as CLOSE_WAIT status and eat up the resources.   (was: In RestliAPIConnector, we only consume the HttpEntity but not close the response, which potentially leave the socket as CLOSE_WAIT status and eat up the resources. )

> Make RestliAPIConnector be able to close the connection finally
> ---------------------------------------------------------------
>
>                 Key: GOBBLIN-1616
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1616
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: Zihan Li
>            Priority: Major
>
> In RestApiConnector, we only consume the HttpEntity but not close the response, which potentially leave the socket as CLOSE_WAIT status and eat up the resources. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)