Installing the Data Fabric Client on Mac OS X (Non-FIPS)
This section describes how to install the Data Fabric client on Mac OS X.
getgroups
command returns a maximum of 16 groups for a user. If the Mac OS user for which you are
installing the client attempts to read or write to a Data Fabric filesystem resource as a member of a group that was not included
in the list of 16 groups returned by getgroups
, file permission errors may
result.- Install the OpenSSL 1.1.1 package and add paths to the OpenSSL 1.1.1 command and dynamic libraries, as described in Installing OpenSSL 1.1.1 for the Mac Client.
- Install or update bash to ensure that the bash version is 4.0.0 or
higher:
brew install bash
- Install or update
gnu-getopt
, which is needed to configure Hadoop later in this procedure:brew install gnu-getopt
-
Create the
/opt
directory:sudo mkdir -p /opt
-
Download the file for the version that you want to install:IMPORTANT To access the Data Fabric internet repository, you must specify the user name (email) and token of an HPE Passport account. For more information, see Using the HPE Ezmeral Token-Authenticated Internet Repository.
https://package.ezmeral.hpe.com/releases/<version>/mac/<mapr-client package name>
-
Open the Terminal application.
- Import the
package keys to enable signature
verification:
Optionally, you may use commands to verify the signatures before installing the software. For more information, see HPE GPG Public Keys for GPG or RPM Signature Verification.wget --user=<email> --password=<token> -O /tmp/maprgpg.key -q https://package.ezmeral.hpe.com/releases/pub/maprgpg.key && rpm --import /tmp/maprgpg.key wget --user=<email> --password=<token> -O /tmp/hpeezdf.pub -q https://package.ezmeral.hpe.com/releases/pub/hpeezdf.pub && rpm --import /tmp/hpeezdf.pub && gpg --import /tmp/hpeezdf.pub
-
Extract
mapr-client-<version>.tar.gz
into the/opt
directory:sudo tar -C /opt -zxf mapr-client-<version>.tar.gz*
- Make sure the client is running JDK 11 or later:
$ echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home $ /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/java -version openjdk version "11.0.1" 2018-10-16 OpenJDK Runtime Environment 18.9 (build 11.0.1+13) OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)
-
Before running
For example:configure.sh
, make sure thatJAVA_HOME
is set correctly for the client in the following script:/opt/mapr/conf/env.sh
$ export JAVA_HOME=$(/usr/libexec/java_home)
-
To use this client with a secure cluster or clusters, copy the following files from the
/opt/mapr/conf
directory on the cluster to the/opt/mapr/conf
directory on the client:ssl_truststore
ssl-client.xml
maprtrustcreds.jceks
maprtrustcreds.conf
If this client will connect to multiple clusters, you must merge the
ssl_truststore
files on the server by using the/opt/mapr/server/manageSSLKeys.sh
tool, and then copy the merged file to/opt/mapr/conf
on the client. For an example of merging thessl_truststore
files, see step 3 in Configuring Secure Clusters for Running Commands Remotely. -
Run
configure.sh
to configure the client. On the Mac client, you must runconfigure.sh
from the/usr/local/bin/bash
directory. In the following examples:
To ensure that the client can connect in the event of a CLDB node failure, all CLDB nodes are specified. For more information about the syntax, parameters, and behavior of-N
(uppercase)Specifies the cluster name -c
(lowercase)Specifies a client configuration -secure
Indicates that the cluster is secure -C
(uppercase)Specifies the CLDB nodes -HS
Specifies the HistoryServer node configure.sh
, see configure.sh.Secure cluster examplesudo /usr/local/bin/bash /opt/mapr/server/configure.sh -N my.cluster.com -c -secure -C mynode01:7222,mynode02:7222,mynode03:7222
Non-secure cluster examplesudo /usr/local/bin/bash /opt/mapr/server/configure.sh -N my.cluster.com -c -C mynode01:7222,mynode02:7222,mynode03:7222 -HS nodeA
NOTEIf the cluster was configured with a cluster-admin
user:group
that is different from the defaultmapr:mapr
value, you must include options to specify the cluster-admin user and group information when you runconfigure.sh
to configure the client.If the cluster-admin user ID is present on the client node, include these options:-u
-g
If the cluster-admin user ID is not present on the client node, include these options:-u
-g
--create-user | -a
-U
-G
-
At the end of the client installation, run the maprlogin password command to create a valid ticket to connect to the cluster.
- Configure Hadoop to enable Hadoop jobs to run on the Mac OS
client:
/opt/mapr/hadoop/hadoop-2.7.6/bin/configure.sh --unsecure -EC "-HS centos.cluster.com --client"