Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Currently the TxnHandler uses 2 connection pools to communicate with the HMS: the default one and one for mutexing. If compaction is configured incorrectly (e.g. too many Initiators are running on the same db) then compaction can use up all the connections in the default connection pool and all user queries can get stuck.
We should have a separate connection pool (configurable size) just for compaction-related activities.
Attachments
Issue Links
- links to
1.
|
Create a new connection pool for compaction (CompactionTxnHandler) | Resolved | Unassigned | |||||||||
2.
|
Create a new connection pool for compaction (DataNucleus) | Resolved | Antal Sinkovits |
|