hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3481) <Resource leak>: Hiveserver is not closing the existing driver handle before executing the next command. It results in to file handle leaks.
Date Wed, 09 Jan 2013 10:29:59 GMT

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

Hudson commented on HIVE-3481:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3481: <Resource leak>: Hiveserver is not closing the existing driver handle
before executing the next command. It results in to file handle leaks. (Kanna Karanam via
Ashutosh Chauhan) (Revision 1393051)

     Result = ABORTED
hashutosh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1393051
Files : 
* /hive/trunk/service/src/java/org/apache/hadoop/hive/service/HiveServer.java

                
> <Resource leak>: Hiveserver is not closing the existing driver handle before executing
the next command. It results in to file handle leaks.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3481
>                 URL: https://issues.apache.org/jira/browse/HIVE-3481
>             Project: Hive
>          Issue Type: Bug
>          Components: JDBC, ODBC, Server Infrastructure
>    Affects Versions: 0.10.0, 0.9.1
>            Reporter: Kanna Karanam
>            Assignee: Kanna Karanam
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3481.1.patch.txt
>
>
> Close the driver object if it exists before creating another driver object. Bunch of
HiveServer & JDBC related unit tests are failing because of these file handle leaks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message