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

Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2015/09/09 22:20:46 UTC

[jira] [Resolved] (AMBARI-13039) Optimize precision table Region split policy for AMS

     [ https://issues.apache.org/jira/browse/AMBARI-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Wagle resolved AMBARI-13039.
--------------------------------------
    Resolution: Fixed

Pushed to trunk and branch-2.1

> Optimize precision table Region split policy for AMS
> ----------------------------------------------------
>
>                 Key: AMBARI-13039
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13039
>             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
>
>
> - In light of AMBARI-12983, performance would be seen if the precision table can fully utilize the allocated memstore heap.
> - With the single table getting most of the high volume reads and all of the high volume writes it is important to define a policy for splitting the Region in order to optimize performance of the scans.



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