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

Posted to issues@hive.apache.org by "Yu-Wen Lai (Jira)" <ji...@apache.org> on 2022/07/22 21:35:00 UTC

[jira] [Resolved] (HIVE-26399) Make DataNucleus use existing connection for value generation

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

Yu-Wen Lai resolved HIVE-26399.
-------------------------------
    Resolution: Won't Do

I found toggling this property sometimes causes db operations never end, but I cannot figure out why at this time. So, I will just close this ticket.

> Make DataNucleus use existing connection for value generation
> -------------------------------------------------------------
>
>                 Key: HIVE-26399
>                 URL: https://issues.apache.org/jira/browse/HIVE-26399
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Yu-Wen Lai
>            Assignee: Yu-Wen Lai
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> DataNucleus by default uses a new connection for value generation, so for one thread it might take two connections at a time. That causes a problem when there are many concurrent requests coming in HMS. If all threads are waiting for a new connection, then no threads can proceed.
> We can set  datanucleus.valuegeneration.transactionAttribute to "EXISTING" so that DataNucleus will take existing connection rather than request a new one from pool.
> Ref:
> https://www.datanucleus.org/products/accessplatform/jdo/persistence.html#pmf_properties
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)