You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Attila Szabo (JIRA)" <ji...@apache.org> on 2016/07/01 13:23:11 UTC

[jira] [Commented] (SQOOP-2971) OraOop does not close connections properly

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

Attila Szabo commented on SQOOP-2971:
-------------------------------------

Hi [~vasas],

I've reviewed it again, and now it seems to be the proper solution. Thanks for you contribution!

Dear [~kathleen]
Could you please also check the change, and if you would find it good as well would you please make it merged?

Many thanks!

> OraOop does not close connections properly
> ------------------------------------------
>
>                 Key: SQOOP-2971
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2971
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Attila Szabo
>            Assignee: Szabolcs Vasas
>             Fix For: 1.4.6, 1.4.7
>
>         Attachments: SQOOP-2971.patch, SQOOP-2971.patch
>
>
> When importing with OraOop for every mapper task two connections are created, and those connections are not closed until the end of the import process, thus Sqoop use twice of the necessary amount, and kinda leaks the expensive resources. This could cause problem when the number of the connections is limited on the DB server side, however the user would like to leverage from having more mappers (e.g. right now with 10 avail connections the user cannot use 10 mappers, but instead only 4).
> Please provide a fix for this issue either by sharing the connection, or closing the connections when they are not needed anymore.



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