[
https://issues.apache.org/jira/browse/SQOOP-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348391#comment-15348391
]
Markus Kemper commented on SQOOP-2971:
--------------------------------------
Thank you [~vasas],
In the field we have seen this issue result in the following Oracle exception
thus limited the degree of parallelism possible when SESSIONS are capped.
16/04/12 13:26:22 INFO mapreduce.Job: Task Id :
attempt_1459758835311_12642_m_000007_0, Status : FAILED
Error: java.lang.RuntimeException: java.lang.RuntimeException:
java.sql.SQLException: ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
at org.apache.sqoop.mapreduce.db.DBInputFormat.setConf(DBInputFormat.java:167)
at org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:73)
at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:133)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:749)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
Caused by: java.lang.RuntimeException: java.sql.SQLException: ORA-02391:
exceeded simultaneous SESSIONS_PER_USER limit
> 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
>
>
> 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)
