[ https://issues.apache.org/jira/browse/HIVE-26419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yu-Wen Lai resolved HIVE-26419. ------------------------------- Resolution: Fixed Thank [~jfs] and [~dkuzmenko] for reviewing the patch. > Use a different pool for DataNucleus' secondary connection factory > ------------------------------------------------------------------ > > Key: HIVE-26419 > URL: https://issues.apache.org/jira/browse/HIVE-26419 > Project: Hive > Issue Type: Bug > Components: Standalone Metastore > Reporter: Yu-Wen Lai > Assignee: Yu-Wen Lai > Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Quote from DataNucleus documentation: > {quote}The secondary connection factory is used for schema generation, and > for value generation operations (unless specified to use primary). > {quote} > We should not use same connection pool for DataNucleus' primary and secondary > connection factory. An awful situation is that each thread holds one > connection and request for another connection for value generation, but no > connection is available in the pool. It will keep retrying and fail at the > end. -- This message was sent by Atlassian Jira (v8.20.10#820010)