[HIVE-26419] Use a different pool for DataNucleus' secondary connection factory

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Standalone Metastore
• Labels: pull-request-available
• Assignee: Yu-Wen Lai
• Reporter: Yu-Wen Lai
• Created: 21/Jul/22 17:42
• Updated: 26/Jul/22 07:03
• Resolved: 26/Jul/22 07:03

Description

Quote from DataNucleus documentation:

The secondary connection factory is used for schema generation, and for value generation operations (unless specified to use primary).

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.

Issue Links

• links to: GitHub Pull Request #3466