The node on which you run the installer and the nodes you plan to include in your cluster must meet certain user, connectivity, and security requirements.
0022 on all nodes in the cluster.
You can change the umask setting in the /etc/profile file, or in the
.cshrc or .login file. The root
user must have a 0022 umask because the cluster admin user requires
access to all files and directories under the /opt/mapr directory,
even those initially created by root services.| Ubuntu Nodes | Red Hat / CentOS Nodes | SUSE Nodes |
|---|---|---|
|
|
|
*The curl version must be greater than 7.51.0.
ERROR: Unable to install dependencies (installer). Ensure that a core OS repo is enabled and retry mapr-setup.shFor more information about the supported Java JDK versions, see the JDK Support Matrix and Java.
mapr-setup.sh must be accessible on the Installer node to all nodes that you want to include in the cluster.The installation process requires a valid cluster admin user to be present on all nodes in
the cluster. The Installer can create a user (the
mapr user) for you or use a user that you have created. If you choose to
create a cluster admin user, make sure the following conditions are met:
mapr user and root user must be configured to use
bash. Other shells are not supported.If the user is not a valid user, installation errors can result. For information about creating the user, see Managing Users and Groups.
If you choose to have the Installer create the user, the Installer runs the following command to add a local user to serve as the cluster admin user:
useradd -m -u $MAPR_UID -g $MAPR_GID -G $(stat -c '%G' /etc/shadow) $MAPR_USERmapr./home/mapr.The installer also adds the following to the MAPR_USER .bashrc file:
[[ -f {{ mapr_home }}/conf/env.sh ]] && . {{ mapr_home }}/conf/env.shNodes that you want to include in the cluster must meet the following criteria:
SUSEConnect -p sle-module-python2/15.<version>/x86_64SUSEConnect -p sle-module-development-tools/15.<version>/x86_64SUSEConnect -l command.The no_proxy environment variable must be set.
Nodes in the cluster need to be able to
communicate without the use of a proxy. If the https_proxy and
http_proxy environment variable is set for nodes in the
cluster, you must also set the no_proxy environment variable for
the cluster admin user and the root user on each node. Configure
the no_proxy environment variable to the IP range of the nodes or to the sub-domain that contains the nodes.
In addition, you must follow this guideline from the Python documentation: "The no_proxy
environment variable can be used to specify hosts which shouldn't be reached via
proxy; if set, it should be a comma-separated list of hostname suffixes,
optionally with :port appended, for example
cern.ch,ncsa.uiuc.edu,some.host:8080."
169.254.169.254The global proxy for package repositories must be set.
/etc/yum.conf./etc/apt/apt.conf.Before installing or upgrading software using the Installer, make sure that you have reviewed the list of known vulnerabilities in Security Vulnerabilities. If a vulnerability applies to your release, contact your support representative for a fix, and apply the fix immediately, if applicable.
When you run the Installer on nodes in the cloud, you must:
Verify that port 9443 is open.
The Installer requires that this port is available.
Ensure that the Installer and service UI URLs should refer to an external URL and not an internal URL.
For example, when you open the Installer URL, replace any internal hostname or IP address with its associated external address. For Amazon EC2 and Google Compute Engine (GCE) clusters, the Installer automatically translates internal addresses to external addresses.
root or a user with
sudo permissions.