Home > Articles > Programming > Java

Applied Big Data Analysis in the Real World with MapReduce and Hadoop

In the third article in this series, Java programming expert Steven Haines demonstrates how to build a meaningful Hadoop MapReduce application to analyze hourly website usage from a set of Apache HTTP Server logs. Learn how to analyze a business problem the MapReduce way and then how to structure key and value types to fit the MapReduce model.

Editor's Note: This is the third article in a three-part series. Be sure to read the first two articles:

Big Data Analysis with MapReduce and Hadoop
Building a MapReduce Application with Hadoop

Like this article? We recommend

The last two articles presented and overview of Hadoop and its architecture and then demonstrated how to build the WordCount application, which is the “Hello, World” sample application in the MapReduce domain. This article builds upon that foundation and demonstrates how to apply MapReduce to a real-world problem: log file analysis.

Visits Per Hour

A common metric that web analytic tools provide about website traffic is the number of page views on a per-hour basis. This helps you better understand the patterns of your users, which can be used to expand and contract your environment if you are running on an elastic platform. For example, if your peak load is from 6pm-8pm but you have virtually no traffic from 3am-6am, then you can scale down your environment in the middle of the night to save costs and you can scale up at 6pm so that your environment can support your load.

In order to compute the number of page visits for each hour, the strategy this example employs is to create a custom Key class that encapsulates an hour (day, month, year, and hour) and then map that key to the number of observed page views for that hour. Just as we did with the WordCount example, the mapper will return the key mapped to the value 1, and then the reducer and combiners will compute the actual count of occurrences for each hour.

The challenge that we’ll face in this example, as opposed to the word count example, is that we need to create a custom key class to hold our date. Building a custom key class is not hard, but it requires that we build a class that implements WritableComparable and override the following three methods:

  • readFields(): Reads the object’s fields from a DataInput object.
  • write(): Writes the object’s fields to a DataOutput object.
  • compareTo(): Standard comparable method that compares this object to another object of the same type.

In this example, we build a reusable DateWritable object, named similar to an IntWritable, that persists a date to and from a binary data object, shown in listing 1.

Listing 1. DateWritable.java

package com.geekcap.hadoopexamples;

import java.text.SimpleDateFormat;
import java.util.Date;
import java.io.DataInput;
import java.io.DataOutput;
import java.io.IOException;

import org.apache.hadoop.io.WritableComparable;

public class DateWritable implements WritableComparable<DateWritable>
	private final static SimpleDateFormat formatter = new SimpleDateFormat( "yyyy-MM-dd' T 'HH:mm:ss.SSS" );
	private Date date;
	public Date getDate()
		return date;
	public void setDate( Date date )
		this.date = date;
	public void readFields( DataInput in ) throws IOException 
		date = new Date( in.readLong() );
	public void write( DataOutput out ) throws IOException 
		out.writeLong( date.getTime() );
	public String toString() 
		return formatter.format( date);

    public int compareTo( DateWritable other )
        return date.compareTo( other.getDate() );

The DateWritable class is straightforward: It wraps a date, implements the readFields() method by reading the date in as a long, and writes the date out to the DataOutput by converting the date to a long. Finally, the comparison is delegated to the Date class’s compareTo() method.

With this key in place, the next step is to build a Hadoop class that uses this key in a mapper, build a reducer, and assemble it into a workable application. Listing 2 shows the code for the LogCountsPerHour Hadoop application.

Listing 2. LogCountsPerHour.java

package com.geekcap.hadoopexamples;

import org.apache.hadoop.conf.Configured;
import org.apache.hadoop.util.Tool;
import org.apache.hadoop.util.ToolRunner;
import org.apache.hadoop.conf.Configuration;
import org.apache.hadoop.fs.Path;
import org.apache.hadoop.io.Text;
import org.apache.hadoop.io.IntWritable;
import org.apache.hadoop.io.LongWritable;
import org.apache.hadoop.mapred.Mapper;
import org.apache.hadoop.mapred.Reducer;
import org.apache.hadoop.mapred.JobConf;
import org.apache.hadoop.mapred.MapReduceBase;
import org.apache.hadoop.mapred.OutputCollector;
import org.apache.hadoop.mapred.Reporter;
import org.apache.hadoop.mapred.KeyValueTextInputFormat;
import org.apache.hadoop.mapred.TextOutputFormat;
import org.apache.hadoop.mapred.JobClient;
import org.apache.hadoop.mapred.FileInputFormat;
import org.apache.hadoop.mapred.FileOutputFormat;

import java.io.IOException;
import java.util.Calendar;
import java.util.Iterator;

public class LogCountsPerHour extends Configured implements Tool {

    public static class LogMapClass extends MapReduceBase
            implements Mapper<LongWritable, Text, DateWritable, IntWritable>
        private DateWritable date = new DateWritable();
        private final static IntWritable one = new IntWritable( 1 );

        public void map( LongWritable key, // Offset into the file
                         Text value,
                         OutputCollector<DateWritable, IntWritable> output,
                         Reporter reporter) throws IOException
            // Get the value as a String; it is of the format:
        	// - - [16/Dec/2012:05:32:50 -0500] "GET / HTTP/1.1" 200 14791 "-" "Mozilla/5.0 (compatible; Baiduspider/2.0; +http://www.baidu.com/search/spider.html)"
            String text = value.toString();
            // Get the date and time
            int openBracket = text.indexOf( '[' );
            int closeBracket = text.indexOf( ']' );
            if( openBracket != -1 && closeBracket != -1 )
            	// Read the date
            	String dateString = text.substring( text.indexOf( '[' ) + 1, text.indexOf( ']' ) );

            	// Build a date object from a string of the form: 16/Dec/2012:05:32:50 -0500
                int index = 0;
                int nextIndex = dateString.indexOf( '/' );
                int day = Integer.parseInt( dateString.substring(index, nextIndex) );

                index = nextIndex;
                nextIndex = dateString.indexOf( '/', index+1 );
                String month = dateString.substring( index+1, nextIndex );

                index = nextIndex;
                nextIndex = dateString.indexOf( ':', index );
                int year = Integer.parseInt(dateString.substring(index + 1, nextIndex));

                index = nextIndex;
                nextIndex = dateString.indexOf( ':', index+1 );
                int hour = Integer.parseInt(dateString.substring(index + 1, nextIndex));

                // Build a calendar object for this date
                Calendar calendar = Calendar.getInstance();
                calendar.set( Calendar.DATE, day );
                calendar.set( Calendar.YEAR, year );
                calendar.set( Calendar.HOUR, hour );
                calendar.set( Calendar.MINUTE, 0 );
                calendar.set( Calendar.SECOND, 0 );
                calendar.set( Calendar.MILLISECOND, 0 );

                if( month.equalsIgnoreCase( "dec" ) )
                    calendar.set( Calendar.MONTH, Calendar.DECEMBER );
                else if( month.equalsIgnoreCase( "nov" ) )
                    calendar.set( Calendar.MONTH, Calendar.NOVEMBER );
                else if( month.equalsIgnoreCase( "oct" ) )
                    calendar.set( Calendar.MONTH, Calendar.OCTOBER );
                else if( month.equalsIgnoreCase( "sep" ) )
                    calendar.set( Calendar.MONTH, Calendar.SEPTEMBER );
                else if( month.equalsIgnoreCase( "aug" ) )
                    calendar.set( Calendar.MONTH, Calendar.AUGUST );
                else if( month.equalsIgnoreCase( "jul" ) )
                    calendar.set( Calendar.MONTH, Calendar.JULY );
                else if( month.equalsIgnoreCase( "jun" ) )
                    calendar.set( Calendar.MONTH, Calendar.JUNE );
                else if( month.equalsIgnoreCase( "may" ) )
                    calendar.set( Calendar.MONTH, Calendar.MAY );
                else if( month.equalsIgnoreCase( "apr" ) )
                    calendar.set( Calendar.MONTH, Calendar.APRIL );
                else if( month.equalsIgnoreCase( "mar" ) )
                    calendar.set( Calendar.MONTH, Calendar.MARCH );
                else if( month.equalsIgnoreCase( "feb" ) )
                    calendar.set( Calendar.MONTH, Calendar.FEBRUARY );
                else if( month.equalsIgnoreCase( "jan" ) )
                    calendar.set( Calendar.MONTH, Calendar.JANUARY );

                // Output the date as the key and 1 as the value
                date.setDate( calendar.getTime() );
                output.collect(date, one);

    public static class LogReduce extends MapReduceBase
            implements Reducer<DateWritable, IntWritable, DateWritable, IntWritable>
        public void reduce( DateWritable key, Iterator<IntWritable> values,
                            OutputCollector<DateWritable, IntWritable> output,
                            Reporter reporter) throws IOException
            // Iterate over all of the values (counts of occurrences of this word)
            int count = 0;
            while( values.hasNext() )
                // Add the value to our count
                count += values.next().get();

            // Output the word with its count (wrapped in an IntWritable)
            output.collect( key, new IntWritable( count ) );

    public int run(String[] args) throws Exception
        // Create a configuration
        Configuration conf = getConf();

        // Create a job from the default configuration that will use the WordCount class
        JobConf job = new JobConf( conf, LogCountsPerHour.class );

        // Define our input path as the first command line argument and our output path as the second
        Path in = new Path( args[0] );
        Path out = new Path( args[1] );

        // Create File Input/Output formats for these paths (in the job)
        FileInputFormat.setInputPaths( job, in );
        FileOutputFormat.setOutputPath( job, out );

        // Configure the job: name, mapper, reducer, and combiner
        job.setJobName( "LogAveragePerHour" );
        job.setMapperClass( LogMapClass.class );
        job.setReducerClass( LogReduce.class );
        job.setCombinerClass( LogReduce.class );

        // Configure the output
        job.setOutputFormat( TextOutputFormat.class );
        job.setOutputKeyClass( DateWritable.class );
        job.setOutputValueClass( IntWritable.class );

        // Run the job
        return 0;

    public static void main(String[] args) throws Exception
        // Start the LogCountsPerHour MapReduce application
        int res = ToolRunner.run( new Configuration(),
                new LogCountsPerHour(),
                args );
        System.exit( res );

The LogCountsPerHour class looks similar to the WordCount class in the previous article, but with a few variances:

  • It defines a new mapper class called LogMapClass that emits DateWritable keys instead of Text keys.
  • Its reducer is nearly identical to our previous reducer, but instead of emitting Text keys and a count, it emits DateWritable keys and a count.
  • The run() method configures the class to run the appropriate mapper, reducer, and combiner as well as configures the output key (DateWritable) and output value (IntWritable).

The most interesting part of the LogCountsPerHour class is the mapper. In short, it parses an Apache Web Server log file line in the following format: - - [16/Dec/2012:05:32:50 -0500] "GET /  HTTP/1.1" 200 14791 "-" "Mozilla/5.0 (compatible;  Baiduspider/2.0; +http://www.baidu.com/search/spider.html)"

And from that it extracts the date:

16/Dec/2012:05:32:50 -0500

And from that it extracts the day, month, year, and hour of the request. This means that all requests between 5:00 and 5:59:59 will be grouped together as a date object for the specified day at 5am. This date will become the Key in our mapper, which means that when, for each record we output this hour and a count of 1, the combiners and reducers will ultimately compute the number of requests for that hour.

The output from running this MapReduce application is the following (I downloaded all of the log files from GeekCap.com, which has a rather poor attendance—please visit me):

2012-11-18 T 16:00:00.000       1
2012-11-18 T 17:00:00.000       21
2012-11-18 T 18:00:00.000       3
2012-11-18 T 19:00:00.000       4
2012-11-18 T 20:00:00.000       5
2012-11-18 T 21:00:00.000       21
2012-12-17 T 14:00:00.000       30
2012-12-17 T 15:00:00.000       60
2012-12-17 T 16:00:00.000       40
2012-12-17 T 17:00:00.000       20
2012-12-17 T 18:00:00.000       8
2012-12-17 T 19:00:00.000       31
2012-12-17 T 20:00:00.000       5
2012-12-17 T 21:00:00.000       21

This analysis shows that at 9pm on November 18 we saw 21 page views at 5pm, and on December 17 we saw 60 page views at 3pm. GeekCap.com is still pretty obscure, but your task (if you run this type of analysis of your production environment) is to look for patterns in daily usage and adapt your environment to react to this usage.

Listing 3 shows the contents of a Maven POM file that can be used to build this. A build can be performed with the following command:

mvn clean install

Listing 3. pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">






This is the same POM file that was used in the previous WordCount example: it defines hadoop-core as the required dependency to compile the code.


This three-part series began by reviewing the domain of problems that MapReduce, and specifically Hadoop, is proficient at solving as well as the architecture that affords Hadoop its power. It presented the basics of building a MapReduce application and running it in Hadoop. It concluded with a real-world MapReduce application that analyzed a web server’s log file and computed the number of page visits per hour.

The key to writing powerful MapReduce applications is to think in terms of mappers, combiners, and reducers. Here are some questions to ponder:

  • What exactly should your key look like?
  • What is the business value that you are trying to derive, and how can you group metrics together into keys?
  • What is the nature of the values you want to compute, and how can that be captured in your Value objects?

Combiners can greatly improve performance, but what conditions must you implement in order to use a combiner? For example, if your reduction operation is not associative then using it as a combiner might disrupt the response, but rewriting it in an associative manner, which means thinking about alternate means of writing the reducer, can have a profound impact on the performance of your application.

In the example presented in this article, the business value we wanted to derive was the number of page visits per hour, so naturally our key should be individual hours. The reason is that if we want to group page visits by hours and see the count on a per-hour basis, then we need to define a key type to match this grouping. When it comes to the value, we wanted a count of the number of pages views, so it made sense that we could use a simple counter. And because addition operations are associative, our reducer could be used as a combiner as well.

I recommended it in the previous article, but I’ll remind you again here: If you are looking for a good book to help you think in the MapReduce way, O’Reilly’s MapReduce Design Patterns is a great choice. I read through several books to help me get Hadoop setup and configured, but MapReduce Design Patterns was the first book that I found that helped me really understand how to approach MapReduce problems. I highly recommend it!

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020