Installing the MapR Client on Ubuntu

This section describes how to install the MapR Client on Ubuntu.

  1. Remove any previous MapR software.

    You can use dpkg --list | grep mapr to get a list of installed MapR packages, then type the packages separated by spaces after the dpkg -r command. Example: dpkg -l | grep mapr.

    dpkg -r mapr-core mapr-fileserver 
  2. Update your Ubuntu repositories.
    Example:
    apt-get update
  3. Run the following command to install the MapR client:
    apt-get install mapr-client
  4. To use this client with a secure cluster or clusters, copy the ssl_truststore file from the /opt/mapr/conf directory on the cluster to the /opt/mapr/conf directory on the client.
    If this client will connect to multiple clusters, merge the ssl_truststore files with the /opt/mapr/server/manageSSLKeys.sh tool.
  5. Run configure.sh to configure the client. In the following examples, the -N parameter specifies the cluster name, the -c (lowercase) parameter specifies a client configuration, the -secure parameter is added if the cluster is secure, the -C (uppercase) parameter specifies the CLDB nodes, and the -HS parameter specifies the HistoryServer node. 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 configure.sh, see configure.sh.
    Non-secure cluster example
    /opt/mapr/server/configure.sh -N my.cluster.com -c -C mynode01:7222,mynode02:7222,mynode03:7222 -HS mynode02
    Secure cluster example
    /opt/mapr/server/configure.sh -N my.cluster.com -c -secure -C mynode01:7222,mynode02:7222,mynode03:7222 -HS mynode02
    Note:

    If the cluster was configured with a cluster-admin user:group that is different from the default mapr:mapr value, you must include options to specify the cluster-admin user and group information when you run configure.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