You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/10/18 16:17:00 UTC
[jira] [Commented] (AMBARI-24800) service adviser changes for
cluster specific configs
[ https://issues.apache.org/jira/browse/AMBARI-24800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655516#comment-16655516 ]
Hudson commented on AMBARI-24800:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10229 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10229/])
[AMBARI-24800] service adviser changes for cluster specific (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=91247455a30f4de0a5af8bcfba92302360a47bff])
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
> service adviser changes for cluster specific configs
> ----------------------------------------------------
>
> Key: AMBARI-24800
> URL: https://issues.apache.org/jira/browse/AMBARI-24800
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Env: HDC Spark Data science (m4x4xlarge 16 CPU/64 GB)
> Spark defaults aren't changed in ambari. It is loading with 1 GB spark.executor.memory.
> (Should this be 60-70% of yarn min container size. Need to consider spark.yarn.executor.memoryOverhead)
> Add such logic for "spark.shuffle.io.numConnectionsPerPeer":
> spark.shuffle.io.numConnectionsPerPeer should be configured dynamically based on cluster size.
> Recommandation was to set it to 10 if number of nodes < 10 and remove (so that default value is used) for higher values.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)