Ivan Martynov commented on AMBARI-25505:

I've tested Case #4: "Customer has manually added property to hbase settings 
through UI and installs new mpack with fix."> (4) For this use case I suspect 
that nothing will happen as an mpack can't 
> override already existing settings but may be worth checking out. In the 
> past for specific settings controlled on the OneFS UI service page an mpack 
> could overwrite a customer config. I performed the following steps:

a) New deployment of HDP 3 with with Hbase service installed with mpack (with conductor) 

Stack: HDP-3.1
Name:  HDP-

b) Add property to hbase settings through UI 

c) Install mpack with fix (1.0.3)
ambari-server install-mpack --mpack=isilon-onefs-mpack- --force 

d) Restart Ambari cluster

e) Confirm property shows up in UI under Hbase Service settings

YES. It is in UI under custom HBASE site section.

1. Test passed and behavior is expected.
2. In this scenario we confirmed that customers who has manually added property 
to hbase settings through UI and installs new mpack with fix didn't loose the 
3. Mpack v.1.0.3 is ready to work under this scenario.

> New version of isilon-onefs-mpack (1.0.3)
> -----------------------------------------
>                 Key: AMBARI-25505
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25505
>             Project: Ambari
>          Issue Type: Improvement
>          Components: contrib
>    Affects Versions: trunk, 2.7.0
>         Environment: HDP versions started from  "2.6"
> Ambari started from version "2.7"
>            Reporter: Ivan Martynov
>            Priority: Critical
>              Labels: performance
>             Fix For: trunk, 2.7.0
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> This issue is going under the direction of Dell Technologies.
> We are going to change the code of isilon-onefs-mpack 
> (+[https://github.com/apache/ambari/tree/trunk/contrib/management-packs/isilon-onefs-mpack]+).
> The problem is that a new feature of HBase 2 (AsyncFSWAL) causes worse 
> performance with OneFS. We need to disable this in the Ambari management pack 
> by setting the property name: "hbase.wal.provider" with value: "filesystem" 
> for HBASE. The way to change the property has been already introduced at:
> [https://jira.apache.org/jira/browse/HBASE-15536]
> In section about how to disable AsyncFSWAL:
> {quote}> ...add this in hbase-site.xml
> > \{code}
> >  <property>
> >   <name>hbase.wal.provider</name>
> >   <value>filesystem</value>
> >  </property>
> > \{code}
> {quote}
>  We are going to issue a new version of isilon-onefs-mpack (1.0.3) where we 
> will have some code lines which add this property to HBASE settings. Change 
> of property is applied automatically after installation of HBASE service and 
> installing a new version of mpack.
> Now our code change relates to one file of code: service_advisor.py, other 
> changes are cosmetic (version numbering and comments).
> As well we are going to port the code to all necessary branches of Ambari of 
> older versions which support isilon-onefs-mpack.
> Business Justification: The problem we are working on is that a new feature 
> of HBase 2 (AsyncFSWAL) causes worse performance with OneFS.
> Some Isilon customers which use HBASE with Ambari with OneFS suffer from this 
> problem. The fix should help these customers.
> Available Maintenance Resources: HDFS team of Dell Isilon supports Ambari 
> mpack project.
> Impact: Improve interaction of Isilon with Hadoop

This message was sent by Atlassian Jira

Reply via email to