You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2018/03/01 23:17:00 UTC

[jira] [Updated] (HIVE-18838) investigate potential issue in FixedSizedObjectPool and reenable it

     [ https://issues.apache.org/jira/browse/HIVE-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin updated HIVE-18838:
------------------------------------
    Summary: investigate potential issue in FixedSizedObjectPool and reenable it  (was: investigate potential issue in FixedSizedObjectPool)

> investigate potential issue in FixedSizedObjectPool and reenable it
> -------------------------------------------------------------------
>
>                 Key: HIVE-18838
>                 URL: https://issues.apache.org/jira/browse/HIVE-18838
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Priority: Major
>
> Looks like some bugs are possible with multiple consumers. The memory model assumptions in some places may be too optimistic. 
> For now the pools will be disabled (see Hive-18837), this JIRA is to reenable if needed after a follow up investigation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)