MapR: Installation - Revision history

K mouza: /* Quick Installer Configuration File */

2015-03-27T09:43:11Z

Quick Installer Configuration File

K mouza at 16:15, 26 March 2015

2015-03-26T16:15:41Z

K mouza at 16:12, 26 March 2015

2015-03-26T16:12:49Z

K mouza: /* Quick Installer Configuration File */

2015-03-26T16:10:55Z

Quick Installer Configuration File

K mouza: /* Quick Installer Configuration File */

2015-03-26T16:09:08Z

Quick Installer Configuration File

K mouza: /* Quick Installer Configuration File */

2015-03-26T16:06:32Z

Quick Installer Configuration File

K mouza at 16:01, 26 March 2015

2015-03-26T16:01:07Z

K mouza: /* Interactive Mode Sample Session */

2015-03-26T15:55:37Z

Interactive Mode Sample Session

K mouza: /* Interactive Mode Sample Session */

2015-03-26T15:52:47Z

Interactive Mode Sample Session

K mouza: /* Using the MapR Quick Installer */

2015-03-26T15:52:03Z

Using the MapR Quick Installer

@@ Line 212: / Line 212: @@
 To perform this type of installation, you must first create a configuration file. The example file, config.example, in the /opt/mapr-installer/bin directory shows the expected format of an installation configuration file.
-Here is a working configuration file for one Control Node, which acts like a Data Node as well: [[File:MapR_config.txt]]
+'''Here is a working configuration file for one Control Node, which acts like a Data Node as well:''' [[File:MapR_config.txt]]
 '''Notes:'''

← Older revision		Revision as of 16:15, 26 March 2015
Line 1:		Line 1:
		+	All the following info and more are available in:
		+	*http://doc.mapr.com/display/MapR/Quick+Installation+Guide
		+	*http://doc.mapr.com/display/MapR/Advanced+Installation+Topics
		+
	The MapR quick installer automates the process of configuring a Hadoop cluster and installing MapR software based on node type. You can install the MapR distribution for Hadoop on a set of nodes from any machine that can connect to the nodes. Using the quick installer, you can configure each node in a MapR cluster as one of the following types:		The MapR quick installer automates the process of configuring a Hadoop cluster and installing MapR software based on node type. You can install the MapR distribution for Hadoop on a set of nodes from any machine that can connect to the nodes. Using the quick installer, you can configure each node in a MapR cluster as one of the following types:

← Older revision		Revision as of 16:12, 26 March 2015
Line 237:		Line 237:

	To install Hive client and server components, uncomment and complete the configuration under the [Hive] section in the configuration file. You may configure one or more hostnames on which to install the Hive clients, typically the same hostnames as specified in the [Clients] section. One or more hostnames can also be provided for installation of HiveServer2, and a single hostname on which to install the Hive metastore. The Hive metastore will be configured to use the default Derby database.		To install Hive client and server components, uncomment and complete the configuration under the [Hive] section in the configuration file. You may configure one or more hostnames on which to install the Hive clients, typically the same hostnames as specified in the [Clients] section. One or more hostnames can also be provided for installation of HiveServer2, and a single hostname on which to install the Hive metastore. The Hive metastore will be configured to use the default Derby database.
		+
		+	== Post Installation ==
		+
		+	To complete the post installation process, follow these steps:
		+	#Access the MCS by entering the following URL in your browser, substituting the IP address with the IP address or hostname of a control node in your cluster:
		+	#:https://<ip_address>:8443
		+	#:Compatible browsers include Chrome, Firefox 3.0 and above, Safari (see Browser Compatibility for more information), and Internet Explorer 10 and above.
		+	#If a message about the security certificate appears, click Proceed anyway.
		+	#Log in with the MapR user name and password that you set during the installation.
		+	#To register and apply a license, click Manage Licenses in the upper right corner, and follow the instructions to add a license via the web.
		+	#Create separate volumes so you can specify different policies for different subsets of data. See Managing Data with Volumes for more information.
		+	#Set up topology so the cluster is rack-aware for optimum replication. See Setting up Node Topology for more information.

← Older revision		Revision as of 16:10, 26 March 2015
Line 227:		Line 227:
	*SuSE		*SuSE
	*:<tt>sudo /opt/mapr-installer/bin/install --cfg /opt/mapr/bin/myconfigfile new</tt>		*:<tt>sudo /opt/mapr-installer/bin/install --cfg /opt/mapr/bin/myconfigfile new</tt>
		+
		+	=== Installing Spark Using the Configuration File ===
		+
		+	To install Spark, uncomment and complete the configuration in the [Spark] section of the configuration file. You must specify one or more hostnames to be SparkMaster nodes, which coordinate execution of Spark jobs, and one or more hostnames to serve as the SparkWorker nodes, which execute Spark jobs. You can also modify the Spark memory configuration settings based on your environment.
		+
		+	'''Note:''' Scala 2.10.3 or later is a pre-requisite for Spark installation. Verify that Scala is installed on nodes where you plan to install Spark.
		+
		+	=== Installing Hive Components using the Configuration File ===
		+
		+	To install Hive client and server components, uncomment and complete the configuration under the [Hive] section in the configuration file. You may configure one or more hostnames on which to install the Hive clients, typically the same hostnames as specified in the [Clients] section. One or more hostnames can also be provided for installation of HiveServer2, and a single hostname on which to install the Hive metastore. The Hive metastore will be configured to use the default Derby database.

← Older revision		Revision as of 16:09, 26 March 2015
Line 209:		Line 209:

	Here is a working configuration file for one Control Node, which acts like a Data Node as well: [[File:MapR_config.txt]]		Here is a working configuration file for one Control Node, which acts like a Data Node as well: [[File:MapR_config.txt]]
		+
		+	'''Notes:'''
		+	*For a new installation, all sections must be present in the configuration file, although the [Data_Nodes] and [Client_Nodes] sections can be left empty. For additions to an existing installation, the [Control_Nodes], [Data_Nodes], and [Client_Nodes] must be present, although they can be left empty. Other sections in the configuration file are silently ignored for additions.
		+
		+	*The value of the Disks element of the [Defaults] section provides a fallback in the case where a node is specified in a previous [Control_Nodes], [Data_Nodes], or [Client_Nodes] section without any disk information.
		+
		+	*If the disks were used for a previous MapR installation, you must set ForceFormat to true.
		+	*:ForceFormat reformats the disk, and any existing data will be permanently lost.
		+
		+	*You do not have to specify values for the keys in the [Defaults] section, but each of the keys must be present.
		+
		+	Once the configuration file is created, you can initiate installation with one of the following commands.
		+	*Ubuntu
		+	*:<tt>sudo /opt/mapr-installer/bin/install -K -s --cfg /opt/mapr/bin/myconfigfile new</tt>
		+	*RedHat/CentOS
		+	*:<tt>sudo /opt/mapr-installer/bin/install --cfg /opt/mapr/bin/myconfigfile new</tt>
		+	*SuSE
		+	*:<tt>sudo /opt/mapr-installer/bin/install --cfg /opt/mapr/bin/myconfigfile new</tt>

← Older revision		Revision as of 16:06, 26 March 2015
Line 207:		Line 207:

	To perform this type of installation, you must first create a configuration file. The example file, config.example, in the /opt/mapr-installer/bin directory shows the expected format of an installation configuration file.		To perform this type of installation, you must first create a configuration file. The example file, config.example, in the /opt/mapr-installer/bin directory shows the expected format of an installation configuration file.
		+
		+	Here is a working configuration file for one Control Node, which acts like a Data Node as well: [[File:MapR_config.txt]]

← Older revision		Revision as of 16:01, 26 March 2015
Line 198:		Line 198:

	The quick installer first sets up the control nodes in parallel, then sets up data nodes in groups of ten nodes at a time. Pre-requisite packages are automatically downloaded and installed by the MapR quick installer.		The quick installer first sets up the control nodes in parallel, then sets up data nodes in groups of ten nodes at a time. Pre-requisite packages are automatically downloaded and installed by the MapR quick installer.
		+
		+	== Quick Installer Configuration File ==
		+
		+	Installation with a configuration file is appropriate when:
		+	*You want to perform a non-interactive installation for speed or repetition.
		+	*The target nodes have different disk configurations.
		+	*You want to install an Apache ecosystem component like Spark or Hive.
		+
		+	To perform this type of installation, you must first create a configuration file. The example file, config.example, in the /opt/mapr-installer/bin directory shows the expected format of an installation configuration file.

← Older revision		Revision as of 15:55, 26 March 2015
Line 151:		Line 151:

	'''Note:''' The MapR quick installer uses the same set of disks and partitions for each node in the cluster. To specify disks and partitions individually for each node, use a configuration file.		'''Note:''' The MapR quick installer uses the same set of disks and partitions for each node in the cluster. To specify disks and partitions individually for each node, use a configuration file.
		+
		+	Once you have specified the cluster’s configuration information, the MapR quick installer displays the configuration and asks for confirmation:
		+	<syntaxhighlight>
		+	Current Information (Please verify if correct)
		+	==============================================
		+	Accessibility settings:
		+	Cluster Name: "my.cluster.com"
		+	MapR User Name: "mapr"
		+	MapR Group Name: "mapr"
		+	MapR User UID: "2000"
		+	MapR User GID: "2000"
		+	MapR User Password (Default: mapr): "****"
		+	Functional settings:
		+	WireLevel Security: "n"
		+	MapReduce Services: "n"
		+	YARN: "y"
		+	MapR-DB: "y"
		+	HBase: "n"
		+	Disks to use: "/dev/xvdf,/dev/xvdg"
		+	Client Nodes: ""
		+	Control Nodes: "control-host-01"
		+	Data Nodes: "data-host-01,data-host-02"
		+	Repository (will download core software from here): "http://package.mapr.com/releases"
		+	Ecosystem Repository (will download packages like Pig, Hive etc from here): "http://package.mapr.com/releases/ecosystem"
		+	MapR Version to Install: "4.0.2"
		+	Java Version to Install: "OpenJDK7"
		+	Allow Control Nodes to function as Data Nodes (Not recommended for large clusters): "n"
		+	Local Repository: "n"
		+	Metrics settings:
		+	Metrics DB Host and Port: ""
		+	Metrics DB User Name: ""
		+	Metrics DB User Password: ""
		+	Metrics DB Schema: ""
		+	(c)ontinue with install, (m)odify options, or save current configuration and (a)bort? (c/m/a) [c]: m
		+	</syntaxhighlight>
		+
		+	'''Note:''' Before you proceed with the installation, you can modify various settings. For example, you can set the stripe width (the number of disks in each storage pool) by selecting the sw option from the modification menu. You should also force format your disks if they were previously used in a MapR installation.
		+
		+	As you continue with the installation, the installer prompts you for the login credentials:
		+	<syntaxhighlight>
		+	(c)ontinue with install, (m)odify options, or save current configuration and (a)bort? (c/m/a) [c]: c
		+	SSH Username: root
		+	SSH password: ****
		+	Now running on Added Control Nodes: [control-host-01]
		+	</syntaxhighlight>
		+
		+	The quick installer first sets up the control nodes in parallel, then sets up data nodes in groups of ten nodes at a time. Pre-requisite packages are automatically downloaded and installed by the MapR quick installer.

@@ Line 123: / Line 123: @@
 =  __  __                ____    ___              _          _  _             =
 = |  \/  |  __ _  _ __  |  _ \  |_ _| _ __   ___ | |_  __ _ | || |  ___  _ __ =
-= | |\/| | / _` || '_ \ | |_) |  | | | '_ \ / __|| __|/ _` || || | / _ \| '__|=
+= | |\/| | / _  ||  _ \ | |_) |  | | |  _ \ / __|| __|/ _  || || | / _ \|  __|=
 = | |  | || (_| || |_) ||  _ <   | | | | | |\__ \| |_| (_| || || ||  __/| |   =
-= |_|  |_| \__,_|| .__/ |_| \_\ |___||_| |_||___/ \__|\__,_||_||_| \___||_|   =
+= |_|  |_| \__ _|| .__/ |_| \_\ |___||_| |_||___/ \__|\__,_||_||_| \___||_|   =
 =                 |_|                                                         =
 =                                                                             =

← Older revision		Revision as of 15:52, 26 March 2015
Line 108:		Line 108:

	=== Running the Quick Installer ===		=== Running the Quick Installer ===
		+
		+	To run the quick installer, login as the root user or use sudo, and issue the following command:
		+	<syntaxhighlight>
		+	/opt/mapr-installer/bin/install new
		+	</syntaxhighlight>
		+
		+	==== Interactive Mode Sample Session ====
		+
		+	The following output reflects a typical interactive-mode session with the MapR quick installer.
		+
		+	<syntaxhighlight>
		+	===============================================================================
		+	= =
		+	= __ __ ____ ___ _ _ _ =
		+	= \| \/ \| __ _ _ __ \| _ \ \|_ _\| _ __ ___ \| \|_ __ _ \| \|\| \| ___ _ __ =
		+	= \| \|\/\| \| / _` \|\| '_ \ \| \|_) \| \| \| \| '_ \ / __\|\| __\|/ _` \|\| \|\| \| / _ \\| '__\|=
		+	= \| \| \| \|\| (_\| \|\| \|_) \|\| _ < \| \| \| \| \| \|\__ \\| \|_\| (_\| \|\| \|\| \|\| __/\| \| =
		+	= \|_\| \|_\| \__,_\|\| .__/ \|_\| \_\ \|___\|\|_\| \|_\|\|___/ \__\|\__,_\|\|_\|\|_\| \___\|\|_\| =
		+	= \|_\| =
		+	= =
		+	===============================================================================
		+	Version: 4.0.2.123
		+	An Installer config file is typically used by experienced MapR admins to skip through the interview process.
		+	Do you have a config file (y/n) [n]: n
		+	Enter the hostnames of all the control nodes separated by spaces or commas []: control-host-01
		+	</syntaxhighlight>
		+
		+	'''Note:''' Only 1 or 3 control nodes are supported.
		+
		+	'''Note:''' Hostname resolution of all nodes in the cluster must be consistent across cluster nodes and the multi-node installer's driver node (the node from which the installation is launched). For example, either all nodes must be specified with a fully qualified domain name (FQDN) or none of the nodes can be specified with their FQDN.
		+
		+	<syntaxhighlight>
		+	Enter the hostnames of all the data nodes separated by spaces or commas []: data-host-01,data-host-02
		+	Set MapR User Name [mapr]:
		+	Set MapR User Password [mapr]:
		+	Is this cluster going to run YARN? (y/n) [y]:
		+	Is this cluster going to run MapReduce1? (y/n) [n]:
		+	Is this cluster going to run Apache HBase? (y/n) [n]:
		+	Is this cluster going to run MapR-DB? (y/n) [y]:
		+	Enter the full path of disks for hosts separated by spaces or commas []: /dev/xvdf,/dev/xvdg
		+	</syntaxhighlight>
		+
		+	'''Note:''' The MapR quick installer uses the same set of disks and partitions for each node in the cluster. To specify disks and partitions individually for each node, use a configuration file.