-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46694/#review130647
-----------------------------------------------------------


Ship it!




Ship It!

- Jayush Luniya


On April 26, 2016, 1:55 p.m., Sumit Mohanty wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/46694/
> -----------------------------------------------------------
> 
> (Updated April 26, 2016, 1:55 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk, enis, and Jayush Luniya.
> 
> 
> Bugs: AMBARI-16056
>     https://issues.apache.org/jira/browse/AMBARI-16056
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> In order to utilize SSD as a L2 (bucket) cache, we specify a file location to 
> hbase.bucketcache.ioengine parameter.
> hbase.bucketcache.ioengine=file:<filepath>
> The directory location specified to the above parameter could be non-existent 
> or non-accessible.
> Since ambari-agent runs with root permissions, the proposed change here is to 
> read the 'hbase.bucketcache.ioengine' parameter from hbase configuration and 
> see if it points to a file location (by looking at file: prefix). 
> In case ioengine points to a file, ambari-agent should create the underlying 
> directory and assign appropriate permissions to hbase:hadoop user.
> Activity
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py
>  ee19ee4 
>   
> ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
>  2c466ea 
>   ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py 
> e042fc1 
>   ambari-server/src/test/python/stacks/2.0.6/configs/default_with_bucket.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/46694/diff/
> 
> 
> Testing
> -------
> 
> Ran stack unit tests.
> 
> 
> Thanks,
> 
> Sumit Mohanty
> 
>

Reply via email to