[
https://issues.apache.org/jira/browse/HIVE-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195597#comment-15195597
]
Alan Gates commented on HIVE-13249:
-----------------------------------
Definitely we want it more done more frequently for countOpenTxns. I wasn't
suggesting they should be in the same thread. I see the disconnect now. I was
thinking of AcidHouseKeeperService as a threadpool, but it isn't, it's one
thread.
So I think in general we should consolidate these threads into one pool. We
should think too about whether the initiator, worker, and cleaner threads
should be handled in such a pool as well. But all that's out of the scope of
this JIRA.
For this particular thread I still think we should run it server side and not
client side. Unfortunately for now that means a second HousekeeperService
implementation. But I think it's better to do that and clean it up later than
it is to put the thread pool in the wrong place.
> Hard upper bound on number of open transactions
> -----------------------------------------------
>
> Key: HIVE-13249
> URL: https://issues.apache.org/jira/browse/HIVE-13249
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Affects Versions: 2.0.0
> Reporter: Wei Zheng
> Assignee: Wei Zheng
> Attachments: HIVE-13249.1.patch
>
>
> We need to have a safeguard by adding an upper bound for open transactions to
> avoid huge number of open-transaction requests, usually due to improper
> configuration of clients such as Storm.
> Once that limit is reached, clients will start failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
