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/04/30 22:48:00 UTC

[jira] [Comment Edited] (HIVE-19304) Update templates.py based on config changes in YARN-7142 and YARN-8122

    [ https://issues.apache.org/jira/browse/HIVE-19304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459213#comment-16459213 ] 

Sergey Shelukhin edited comment on HIVE-19304 at 4/30/18 10:47 PM:
-------------------------------------------------------------------

Hmm, unlike the previous logic where placement policy was controlled by a variable, this seems to turn on anti-affinity for all cases.
Is it possible to base it on the variable? We set it when the LLAP container size is > 0.5 YARN node size, avoiding the significant anti-affinity overhead in most cases and only using it when needed.


was (Author: sershe):
Hmm, unlike the previous logic where placement policy was controlled by a variable, this seems to turn on anti-affinity for all cases.
Is it possible to base it on the variable? We set if when the LLAP container size is > 0.5 YARN node size, avoiding the significant anti-affinity overhead in most cases and only using it when needed.

> Update templates.py based on config changes in YARN-7142 and YARN-8122
> ----------------------------------------------------------------------
>
>                 Key: HIVE-19304
>                 URL: https://issues.apache.org/jira/browse/HIVE-19304
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Gour Saha
>            Assignee: Gour Saha
>            Priority: Major
>         Attachments: HIVE-19304.001.patch
>
>
> Now that YARN-7142 is committed and YARN-8122 will be committed soon, we need to update templates.py based on config changes for placement policy and health threshold monitor.



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