core-site.xml

	<property>
		<name>hadoop.tmp.dir</name>
		<value>/data/hdfs/tmp</value>
		<description>Where Hadoop will place all of its working files</description>
	</property>
	<property>
		<name>fs.defaultFS</name>
		<value>hdfs://master:9000</value>
		<description>Where HDFS NameNode can be found on the network</description>
	</property>
	<property>
		<name>hadoop.proxyuser.hduser.groups</name>
		<value>*</value>
		<description>
			What user groups are allow to connect to the HDFS proxy.
			* for all.</description>
	</property>
	<property>
		<name>hadoop.proxyuser.hduser.hosts</name>
		<value>*</value>
		<description>
			What user hosts are allow to connect to the HDFS proxy.
			* for all.
		</description>
	</property>

hdfs-site.xml

	<property>
		<name>dfs.replication</name>
		<value>2</value>
		<description>The default replication factor of files on HDFS</description>
	</property>
	<property> 
		<name>dfs.block.size</name>
		<value>16777216</value>
		<description>The default block size in bytes of data saved to HDFS</description>
	</property>
	<property>
		<name>dfs.namenode.rpc-bind-host</name>
		<value>0.0.0.0</value>
		<description>
			controls what IP address the NameNode binds to. 
			0.0.0.0 means all available.
		</description>
	</property>
	<property>
		<name>dfs.namenode.servicerpc-bind-host</name>
		<value>0.0.0.0</value>
		<description>
			controls what IP address the NameNode binds to. 
			0.0.0.0 means all available.
		</description>
	</property>
	<property>
		<name>dfs.namenode.http-bind-host</name>
		<value>0.0.0.0</value>
		<description>
			controls what IP address the NameNode binds to. 
			0.0.0.0 means all available.
		</description>
	</property>
	<property>
		<name>dfs.namenode.https-bind-host</name>
		<value>0.0.0.0</value>
		<description>
			controls what IP address the NameNode binds to. 
			0.0.0.0 means all available.
		</description>
	</property>
	<property>
		<name>nfs.dump.dir</name>
		<value>/tmp/.hdfs-nfs</value>
		<description>A temporary working directory for files coming into the HDFS proxy.</description>
	</property>
	<property>
		<name>nfs.metrics.percentiles.intervals</name>
		<value>100</value>
		<description>
			Enable the latency histograms for read, write and commit requests. 
			The time unit is 100 seconds in this example.
		</description>
	</property>
	<property>
		<name>nfs.exports.allowed.hosts</name>
		<value>* rw</value>
		<description>Host permissions for connecting to the proxy.</description>
	</property>
	<property>
		<name>dfs.permissions</name>
		<value>true</value>
		<description>Enforce permissions</description>
	</property>
	<property>
		<name>dfs.permissions.supergroup</name>
		<value>hadoop</value>
		<description>The name of the group of Hadoop super-users.</description>
	</property>

mapred-site.xml

	<property>
		<name>mapreduce.framework.name</name>
		<value>yarn</value>
	</property>
	<property>
		<name>mapreduce.map.memory.mb</name>
		<value>256</value>
	</property>
	<property>
		<name>mapreduce.reduce.memory.mb</name>
		<value>384</value>
	</property>
	<property>
		<name>mapreduce.map.java.opts</name>
		<value>-Xmx192m</value>
	</property>
	<property>
		<name>mapreduce.reduce.java.opts</name>
		<value>-Xmx256m</value>
	</property>
	<property>
		<name>mapreduce.job.tracker</name>
		<value>master:5431</value>
	</property>
	<property>
		<name>yarn.app.mapreduce.am.resource.mb</name>
		<value>512</value>
	</property>

yarn-site.xml

	<property>
		<name>yarn.nodemanager.aux-services</name>
		<value>mapreduce_shuffle</value>
	</property>
	<property>
		<name>yarn.nodemanager.resource.memory-mb</name>
		<value>512</value>
	</property>
	<property>
		<name>yarn.scheduler.minimum-allocation-mb</name>
		<value>128</value>
	</property>
	<property>
		<name>yarn.nodemanager.vmem-check-enabled</name>
		<value>false</value>
		<description>Whether virtual memory limits will be enforced for containers</description>
	</property>
	<property>
		<name>yarn.nodemanager.vmem-pmem-ratio</name>
		<value>4</value>
		<description>
			Ratio between virtual memory to physical memory when setting memory 
			limits for containers
		</description>
	</property>	
	<property>
		<name>yarn.resourcemanager.resource-tracker.address</name>
	<value>master:8025</value>
	</property>
	<property>
		<name>yarn.resourcemanager.scheduler.address</name>
		<value>master:8035</value>
	</property>
	<property>
		<name>yarn.resourcemanager.address</name>
		<value>master:8050</value>
	</property>