Ivan Martynov created AMBARI-25505:

             Summary: 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
             Fix For: trunk, 2.7.0

This issue is going under the direction of Dell Technologies.

We are going to change the code of 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:


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}
 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 

Impact: Improve interaction of Isilon with Hadoop

This message was sent by Atlassian Jira

Reply via email to