[
https://issues.apache.org/jira/browse/HIVE-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-11915:
------------------------------------
Attachment: HIVE-11915.02.patch
Updated the patch; fixed the log, moved the retry logic closer to the code.
I disagree about extra retries just-in-case - that's what retrying object store
and ms client do, and 90% of the cases when I see these (and 100% for the
former) is when it blindly retries for some non-recoverable exceptions.
DBCP has been around for a while and doesn't merit doing things just in case,
esp. if there's no way to tell what is recoverable... at least with BONECP we
know what we are trying to fix.
> 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.02.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)
