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

Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/09/17 01:08:46 UTC

[jira] [Commented] (AMBARI-13108) Kafka metrics result in skewed split point distribiution

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

Hudson commented on AMBARI-13108:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #541 (See [https://builds.apache.org/job/Ambari-branch-2.1/541/])
AMBARI-13108. Kafka metrics result in skewed split point distribiution. (swagle) (swagle: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0dfe5769ff449c3f520a6dfb782b7256304d5cde)
* ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/split_points.py


> Kafka metrics result in skewed split point distribiution
> --------------------------------------------------------
>
>                 Key: AMBARI-13108
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13108
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>             Fix For: 2.1.2
>
>
> Out of 2400 data points Kafka metrics take up 1100. In a 400 node cluster this results in an imbalance among the load distribution on the Region Server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)