hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarvesh Sakalanaga (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-4807) Hive metastore hangs
Date Tue, 02 Jul 2013 18:53:20 GMT

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

Sarvesh Sakalanaga updated HIVE-4807:
-------------------------------------

    Description:  Hive metastore hangs (does not accept any new connections) due to a bug
in DPBP. The root cause analysis is here https://issues.apache.org/jira/browse/DBCP-398. 
The fix is to change Hive connection pool to BoneCP which is natively supported by DataNucleus.
The change currently just pulls down BoneCp artifact and does not change the default value
to BoneCP. To enable BoneCp the setting “datanucleus.connectionPoolingType” in hive-site.xml
should be set to “BoneCP”. All the hive systems test pass with this setting.    (was:
 Hive metastore hangs (does not accept any new connections) due to a bug in DPBP. The root
case analysis is here https://issues.apache.org/jira/browse/DBCP-398.  The fix is to change
Hive connection pool to BoneCP which is natively supported by DataNucleus. The change currently
just pulls down BoneCp artifact and does not change the default value to BoneCP. To enable
BoneCp the setting “datanucleus.connectionPoolingType” in hive-site.xml should be set
to “BoneCP”. All the hive systems test pass with this setting.  )
    
> Hive metastore hangs
> --------------------
>
>                 Key: HIVE-4807
>                 URL: https://issues.apache.org/jira/browse/HIVE-4807
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.8.0, 0.9.0, 0.10.0, 0.11.0
>            Reporter: Sarvesh Sakalanaga
>            Assignee: Sarvesh Sakalanaga
>         Attachments: Hive-4807.0.patch
>
>
>  Hive metastore hangs (does not accept any new connections) due to a bug in DPBP. The
root cause analysis is here https://issues.apache.org/jira/browse/DBCP-398.  The fix is to
change Hive connection pool to BoneCP which is natively supported by DataNucleus. The change
currently just pulls down BoneCp artifact and does not change the default value to BoneCP.
To enable BoneCp the setting “datanucleus.connectionPoolingType” in hive-site.xml should
be set to “BoneCP”. All the hive systems test pass with this setting.  

--
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