[
https://issues.apache.org/jira/browse/HIVE-17292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123582#comment-16123582
]
Peter Vary commented on HIVE-17292:
-----------------------------------
Sorry I made a mistake when looking up the stuff again, and copied the wrong
config name.
We have to set {{yarn.scheduler.increment-allocation-mb}} - Notice *increment*
:)
This is a FairScheduler only configuration:
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/FairScheduler.html#Properties_that_can_be_placed_in_yarn-site.xml
??The fairscheduler grants memory in increments of this value. If you submit a
task with resource request that is not a multiple of increment-allocation-mb,
the request will be rounded up to the nearest increment. Defaults to 1024 MB.??
Also see, why is not in the yarn documentation (YARN-5902)
Sorry for the confusion :(
Peter
> Change TestMiniSparkOnYarnCliDriver test configuration to use the configured
> cores
> ----------------------------------------------------------------------------------
>
> Key: HIVE-17292
> URL: https://issues.apache.org/jira/browse/HIVE-17292
> Project: Hive
> Issue Type: Sub-task
> Components: Spark, Test
> Affects Versions: 3.0.0
> Reporter: Peter Vary
> Assignee: Peter Vary
> Attachments: HIVE-17292.1.patch
>
>
> Currently the {{hive-site.xml}} for the {{TestMiniSparkOnYarnCliDriver}} test
> defines 2 cores, and 2 executors, but only 1 is used, because the MiniCluster
> does not allows the creation of the 3rd container.
> The FairScheduler uses 1GB increments for memory, but the containers would
> like to use only 512MB. We should change the fairscheduler configuration to
> use only the requested 512MB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
