diff --git a/README.md b/README.md index 039aa72..d2a7b84 100644 --- a/README.md +++ b/README.md @@ -8,13 +8,25 @@ Version 1.1.0 introduces healthchecks for the containers. * 2.7.1 with OpenJDK 7 * 2.7.1 with OpenJDK 8 -## Description +## Quick Start To deploy an example HDFS cluster, run: ``` docker-compose up ``` +`docker-compose` creates a docker network that can be found by running `docker network list`, e.g. `dockerhadoop_default`. + +Run `docker network inpect` on the network (e.g. `dockerhadoop_default`) to find the IP the hadoop interfaces are published on. Access these interfaces with the following URLs: + +* Namenode: http://:50070/dfshealth.html#tab-overview +* History server: http://:8188/applicationhistory +* Datanode: http://:50075/ +* Nodemanager: http://:8042/node +* Resource manager: http://:8088/ + +## Configure Environment Variables + The configuration parameters can be specified in the hadoop.env file or as environmental variables for specific services (e.g. namenode, datanode etc.): ``` CORE_CONF_fs_defaultFS=hdfs://namenode:8020 @@ -36,11 +48,4 @@ The available configurations are: * /etc/hadoop/httpfs-site.xml HTTPFS_CONF * /etc/hadoop/kms-site.xml KMS_CONF -If you need to extend some other configuration file, refer to base/entrypoint.sh bash script. - -After starting the example Hadoop cluster, you should be able to access interfaces of all the components (substitute domain names by IP addresses from ```network inspect hadoop``` command): -* Namenode: http://namenode:50070/dfshealth.html#tab-overview -* History server: http://historyserver:8188/applicationhistory -* Datanode: http://datanode:50075/ -* Nodemanager: http://nodemanager:8042/node -* Resource manager: http://resourcemanager:8088/ +If you need to extend some other configuration file, refer to base/entrypoint.sh bash script. \ No newline at end of file