Why it is better not to use VirtualBox(VMWare etc..)

Cons

1. VirtualBox can not use full 100% resources of PC. Your hadoop will not be as fast as you expect.

2. You have to start virtual nodes whenever your reboot your PC (unless if you made some auto-start scripts)

3. Several virtual nodes in the same PC can cause mismanagement of resources. If RAM usage of VirtualBox nodes exceeds the maximum then your PC just crashes.

Though, VirtualBox is a good starting point to build experimental hadoop environment.

Pros

1. You can create several nodes in the same PC (if you lack PCs)

2. VirtualBox has Export /Import features that helps you to do "Do once - Copy many"

3. Do experiments by changing hardware features (add CPUs, reduce RAM etc..)

For learning hadoop VirtualBox can be helpful to build hadoop environment.

However, for production purpose it is better to avoid Virtualbox and use PC itself as a single node.

Comments

NLP for Uzbek language

Natural language processing is an essential tool for text mining in data analysis field. In this post, I want to share my approach in developing stemmer for Uzbek language. Uzbek language is spoken by 27 million people around the world and there are a lot of textual materials in internet in uzbek language and it is growing. As I was doing my weekend project " FlipUz " (which is news aggregator for Uzbek news sites) I stumbled on a problem of automatic tagging news into different categories. As this requires a good NLP library, I was not able to find one for Uzbek language. That is how I got a motive to develop a stemmer for Uzbek language. In short, Stemming is an algorithm to remove meaningless suffixes at the end, thus showing the core part of the word. For example: rabbits -> rabbit. As Uzbek language is similar to Turkish, I was curious if there is stemmer for Turkish. And I found this: Turkish St...

Streaming Twitter tweets to HBase with Apache Flume

Apache Hbase is a great noSQL database for storing enormous amount of data that can scale in three axis. Apache Hbase was based on Google's BigTable that stores all web contents in internet. By knowing row key and column id we can retrieve the value at the matter of milliseconds. HBase runs on top of HDFS and friendly with MapReduce tasks. So it can scale up together with Hadoop. One thing which seems to be disadvantage is HBase depends on ZooKeeper, while other big table based databases like Cassandra is independent. Nevertheless, I did not face any problem with it. Apache Hbase is really fast. Currently I am using it for TF-IDF based keyword retrieval, and it can retrieve results from 2 million tweets in few seconds. Anyways, Let me get back to the topic. My plan was to stream twitter data directly to Hbase by using Apache Flume. Fortunately, Flume has a Hbase sink plugin that comes by default in lib folder. We can use two kinds o...

Three essential things to do while building Hadoop environment

Last year I setup Hadoop environment by using Cloudera manager. (Basically I followed this video tutorial : http://www.youtube.com/watch?v=CobVqNMiqww ) I used CDH4(cloudera hadoop) that included HDFS, MapReduce, Hive, ZooKeeper HBase, Flume and other essential components. It also included YARN (MapReduce 2) but it was not stable so I used MapReduce instead. I installed CDH4 on 10 centos nodes, and I set the Flume to collect twitter data, and by using "crontab" I scheduled the indexing the twitter data in Hive. Anyways, I want to share some of my experiences and challenges that I faced. First, let me give some problem solutions that everyone must had faced while using Hadoop. 1. vm.swappiness warning on hadoop nodes It is easy to get rid of this warning by just simply running this shell command on nodes: >sysctl -w vm.swappiness=0 More details are written on cloudera's site 2. Make sure to synchronize time on all nodes (otherwise it will give error on n...

My Technical Blog

Search This Blog