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/01/19 16:49:34 UTC
[jira] [Commented] (AMBARI-9195) Configs: Editing HBase Region
Server Configuration Parameters
[ https://issues.apache.org/jira/browse/AMBARI-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282617#comment-14282617 ]
Hudson commented on AMBARI-9195:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit-docker #796 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/796/])
AMBARI-9195. Configs: Editing HBase Region Server Configuration Parameters (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bcae2e893878790aa5ae7ddbede1e5903d460f27)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
> Configs: Editing HBase Region Server Configuration Parameters
> -------------------------------------------------------------
>
> Key: AMBARI-9195
> URL: https://issues.apache.org/jira/browse/AMBARI-9195
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.0.0
>
>
> The HBase block cache size parameter is editable through Ambari. But HBase
> verifies whether the sum of the value specified for hfile.block.cache.size and
> hbase.regionserver.global.memstore.upperLimit doesn't exceed 0.8 when it
> starts. We would want to make the memstore variables
> (hbase.regionserver.global.memstore.upperLimit and
> hbase.regionserver.global.memstore.upperLimit) editable or at least adjust
> these values automatically if the user changes the block cache size (may not
> be a preferable option).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)