[
https://issues.apache.org/jira/browse/HIVE-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935599#comment-14935599
]
Thejas M Nair commented on HIVE-11915:
--------------------------------------
The retries are being set only for bonecp, but basing the log message on that
seems very brittle. Other developers might add retries for other connection
pooling types by setting getConnAttemptCount, and easily overlook updating the
log message.
Even in case of bonecp exceptions, in some cases the error can be
non-recoverable. This is a fatal error and should be rare. The delay due to
retries likely to be very small (not easily noticeable to the user). I think
that delay would be acceptable for the circumstance.
This looks like a tradeoff between more easy to maintain code and a delay that
users are unlikely to notice.
> BoneCP returns closed connections from the pool
> -----------------------------------------------
>
> Key: HIVE-11915
> URL: https://issues.apache.org/jira/browse/HIVE-11915
> Project: Hive
> Issue Type: Bug
> Reporter: Takahiko Saito
> Assignee: Sergey Shelukhin
> Attachments: HIVE-11915.01.patch, HIVE-11915.WIP.patch,
> HIVE-11915.patch
>
>
> It's a very old bug in BoneCP and it will never be fixed... There are
> multiple workarounds on the internet but according to responses they are all
> unreliable. We should upgrade to HikariCP (which in turn is only supported by
> DN 4), meanwhile try some shamanic rituals. In this JIRA we will try a
> relatively weak drum.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
