[
https://issues.apache.org/jira/browse/HIVE-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544777#comment-14544777
]
Jason Dere commented on HIVE-10711:
-----------------------------------
Not sure if I want to add yet another config param, especially for a last-ditch
fallback which shouldn't happen if the settings are properly done ..
We could use HIVEHASHTABLEFOLLOWBYGBYMAXMEMORYUSAGE, which is the more
conservative memory usage setting for mapjoins (compared to
HIVEHASHTABLEMAXMEMORYUSAGE). Thoughts?
> Tez HashTableLoader attempts to allocate more memory than available when
> HIVECONVERTJOINNOCONDITIONALTASKTHRESHOLD exceeds process max mem
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-10711
> URL: https://issues.apache.org/jira/browse/HIVE-10711
> Project: Hive
> Issue Type: Bug
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: HIVE-10711.1.patch, HIVE-10711.2.patch
>
>
> Tez HashTableLoader bases its memory allocation on
> HIVECONVERTJOINNOCONDITIONALTASKTHRESHOLD. If this value is largeer than the
> process max memory then this can result in the HashTableLoader trying to use
> more memory than available to the process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
