April 30, 2013
- %hadoop namenode -format #This will format the file system
- starting the daemons : %start-dfs.sh ; %start-mapred.sh
- If the configuration files, mentioned in the previous post are in a separate directory run the commands with the –config option : %start-dfs.sh –config path-to-config-directory
- This will start a namenode, a secondary namenode and a datanode
- Commands to close the daemons : stop-dfs.sh and stop-mapred.sh
You should also read up http://gbif.blogspot.com/2011/01/setting-up-hadoop-cluster-part-1-manual.html and then write a post like how the developer machine works and then how the developer machine can connect and run jobs on the hadoop cluster, etc. Then how he can deploy the code, or test the code from his developer machine while development with the hadoop cluster and then how does it changed when the code gets deployed.
April 30, 2013
Common Properties – core-site.xml
HDFS Properties – hdfs-site.xml
MapReduce Properties – mapred-site.xml
The default settings are stored in the docs directory of the hadoop installation for HTML files called : core-default.html, hdfs-default.html, mapred-default.html.
For different configurations :
April 30, 2013
HDFS is a distributed file system and has the following properties:
1. It is optimized for streaming access of large files. You would typically store files that are in the 100s of MB upwards on HDFS and access them through MapReduce to process them in batch mode.
2. HDFS is optimized for use cases where you write once and read many times like in the case of production logs. You can append to files in some of the recent versions but that is not a feature that is very commonly used. There is no concept of random writes.
3. HDFS doesn’t do random reads very well.
HBase on the other hand is a distributed column oriented database. The filesystem of choice typically is HDFS owing to the tight integration between HBase and HDFS. Having said that, it doesn’t mean that HBase can’t work on any other filesystem. It’s just not proven in production and at scale to work with anything except HDFS.
HBase provides you with the following:
1. It gives you the ability to do random read/writes on your data which HDFS doesnt allow you to.
2. HBase stores data in the form of key value pairs in a columnar fashion. HBase provides a flexible data model.
3. Fast scans across tables.
4. Scale in terms of writes as well as total volume of data.
An analogous comparison would be between MySQL and Ext4.
April 26, 2013
pushd, tee, wget, curl, httpd, netstat, tcdump, oprofile,
April 24, 2013
In Java, all the objects are passed by reference. I need to make this understanding of pass by value, reference and pointer clear first. Read it again and again.
Then think about why it is said that everything is passed by reference in java if it is an object.