[
https://issues.apache.org/jira/browse/AMBARI-25505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17096646#comment-17096646
]
Ivan Martynov commented on AMBARI-25505:
----------------------------------------
Test case #2: "Customer performs an mpack upgrade with fix when hbase service
already installed".
Test steps:
a) new deployment of HDP 3 with Hbase service installed with mpack 1.0.2.0.
Stack: HDP-3.1
Name: HDP-3.1.5.0
Type: STANDARD
Version: 3.1.5.0-152
Cluster: hadoop0427
Check installed mpack version:
root@dtseacli629941:~ # ls -l /var/lib/ambari-server/resources/mpacks/
total 12
drwxr-xr-x. 2 root root 4096 Apr 16 06:07 cache
-rw-r--r--. 1 root root 223 Apr 16 06:07 mpacks_replay.log
drwxr-xr-x. 3 root root 4096 Nov 21 04:11 onefs-ambari-mpack-1.0.2.0
root@dtseacli629941:~ #
Do not set the hbase.wal.provider setting:
root@dtseacli629941:/home #
root@dtseacli629941:/home # python
/var/lib/ambari-server/resources/scripts/configs.py --user=admin
--password=admin --port=8080 --action=get --host=localhost --cluster=hadoop0427
--config-type=hbase-site | grep 'hbase.wal.provider'
#
I did not set the hbase.wal.provider setting.
b) upgrade to the new mpack 1.0.3.0
root@dtseacli629941:/home/install # ambari-server upgrade-mpack
--mpack=isilon-onefs-mpack-1.0.3.0.tar.gz --verbose
...
Ambari Server 'upgrade-mpack' completed successfully.
Check upgraded mpack version:
root@dtseacli629941:/home/install # ls -l
/var/lib/ambari-server/resources/mpacks/
total 12
drwxr-xr-x. 2 root root 4096 Apr 16 09:02 cache
-rwxr-xr-x. 1 root root 421 Apr 16 09:02 mpacks_replay.log
drwxr-xr-x. 3 root root 4096 Apr 11 13:40 onefs-ambari-mpack-1.0.3.0
Restart ambari server with the following ambari-server restart
root@dtseacli629941:/home/install # ambari-server restart -v
c) restart ambari server with the following:
ambari-server restart
d) confirm property shows up in UI under OneFS Service settings or Hbase
Service settings
The property hbase.wal.provider didn't show up in UI.
This is an expected behavior, as I read in
> (2) The suggested fix shown in the branch linked in use case above will not
> automatically inject the setting because the hbase service is already
> installed. At least this is base on my understanding based on observation
> and talks with Cloudera. I briefly remember testing this use case. The only
> solution to this use case then is to have the customer manually add the
> config through the UI. e) Add property manually in UI:
<name>hbase.wal.provider</name>
<value>filesystem</value>
f) Restarted services: 4 HBase Clients, 4 RegionServers, 1 HBase Master.
Ambari suggested to restart, so I did.
h) Confirm property shows up in UI under OneFS Service settings or Hbase
Service settings
YES. It is in UI.
Conclusions:
1. Test passed and behavior is expected.
2. In this scenario we recommend customers to add property hbase.wal.provider
with value filesystem manually to HBASE settings through UI after MPack upgrade.
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
(v8.3.4#803005)
