Mon, Jun
3 New Articles

A Small Intro to Big Data, Part 3: HFDS and the MapReduce Algorithm

  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Let's see how data is stored, using Hadoop's File System (HDFS), and processed, using the MapReduce algorithm, in the Hadoop Cluster.

Last time around, I took you on a tour through Hadoop's ecosystem, or in other words, I showed you the main components of its mechanism. Now let's see what makes it tick. Note, however, that this is no easy task, and I won't explain everything in detail. I'll try to keep the explanations simple, but Hadoop is everything but simple.

Let's start with Hadoop's file system, the Hadoop Distributed File System (HDFS). As I mentioned in the previous article, the HDFS is based upon the Google File System (GFS) architecture, which means that, like the GFS, the HDFS is a very resilient piece of computer engineering. The HDFS provides a distributed architecture for extremely large-scale storage, which can easily be extended by scaling out the hardware that supports it. There's an important nuance in the previous sentence. Typically, supercomputers scale up: By adding more resources (more processors, disks, and so on) to the supercomputer itself, performance is improved. With Hadoop and HDFS, it's a bit different: Scaling out means adding more small servers to the cluster, as opposed to adding more resources to one massive supercomputer, when more power or capacity is needed.

In order to scale out, HDFS has some peculiarities. Let's start with the most important: how files are stored. As you'd expect, HDFS is a file system, so it's obvious that it stores files. However, there are a couple of things that you need to know in order to understand how and why the HDFS performs this task. Hadoop can handle structured and unstructured data. The latter usually comes in the form of huge log files (typically larger than 500MB), which a regular file system would have difficulties processing. It's also important to mention that Hadoop was designed to work on a cluster of machines, sharing the workload among them, because none of them by itself can handle the copious amounts of data that need processing. Finally, there are a lot more reads than writes in the HDFS than in a regular file system because Hadoop digests data more often than it ingests: Hadoop's purpose being processing big data sets means that several different analyses are necessarily run over the same chunk of data.

In order to be able to cater to Hadoop's peculiar needs, the HDFS stores files in a particular way. When you save a file in the HDFS, the system breaks it down into blocks and stores these blocks in various slave nodes all over the Hadoop cluster. These blocks don't follow the original file-record markings (for instance, a CSV file can be split midline). Instead, the blocks are created based on the size of the data. HDFS only wants to make sure that files are split into similarly sized blocks that match the predefined block size for the Hadoop instance. Regular file systems also do this. However, Hadoop's file blocks are usually 128MB or larger, while a typical Linux block has 4KB. This is important because the MapReduce (and similar algorithms) will process these blocks in parallel. To enable efficient processing, a balance needs to be struck between the block size and the processing resources available. On one hand, the block size needs to be large enough to warrant the resources dedicated to an individual unit of data processing (typically a cluster node). On the other hand, the block size can't be so large that the system is waiting a very long time for one last unit of data processing to finish its work.

So, a file (usually a large chunk of unstructured data) is split in equal-sized blocks and spread across the Hadoop cluster. Wait...What if one of the cluster nodes fails? After all, we're talking about cheap, off-the-shelf servers. Well, that's where one of the other peculiarities of HDFS kicks in: When the files are split into blocks, HDFS sends the same block to several nodes, thus providing the necessary redundancy that allows the system to keep running smoothly even if some nodes fail. Performance will be affected, but data integrity will be maintained. This block replication process typically sends three copies of each block to different nodes. If a node failure is detected, a fresh copy of the data it contained is replicated to another node in order to comply with the "three-block-copy" principle across the Hadoop cluster.

In short, HDFS's main features are its Write Once, Read Many architecture; file block splitting to enhance parallel processing; and redundancy via replication.

The MapReduce Algorithm (Like Having an Octopus Make Lemonade)

Now that you know how the data is stored, let's see how it can be queried efficiently. In a conventional programming language, like RPG, data is usually processed sequentially. For instance, in order to determine how many records of a table contain a certain value, you'd follow a sequence of actions:

  1. Open the table.
  2. Read the first record (either sequentially from the top or using a key).
  3. Check whether it matches the predefined conditions.
  4. Increment the counter.
  5. Move to the next record, repeating the process until the end of the file is reached.

Naturally, this is a simplistic view of the process, because typically indices are used to speed up the search, and SQL might also come into play. However, the process is still sequential. MapReduce and similar algorithms introduce parallel processing into this logic. Imagine that you're making lemonade with your bare hands; even if you're using two hands, it'll take a while. Now imagine an (intelligent) octopus making lemonade: with its multiple arms, the octopus can perform several tasks simultaneously, or in parallel, and get the job done faster. Hadoop's MapReduce implementation is just that - a way to get things done faster by performing tasks in parallel.

Let's consider an example of finding which "things" match a certain set of conditions. Suppose I want to count how many files in my gigantic dataset contain the word "lemonade." Now remember that the files are scattered over several nodes of the Hadoop cluster. Sequential processing would take forever because I'd have to retrieve each file (just like I'd retrieve each record in the previous example) and analyze it. The MapReduce algorithm solves this problem by splitting the task into two subtasks: mapping (finding where the files that contain pertinent data are) and reducing (applying whichever operation was requested - in this case, it'd be a simple count) over that subset of data. Still, by itself, this wouldn't solve the problem, because there's a lot of data, all over the cluster. That's the beauty of MapReduce: these tasks are executed in parallel in the slave nodes, and the result is then sent to the primary node. Instead of bringing data to the primary node for processing, the code itself is sent to the slave nodes for execution. Only the partial results of each node are sent back, as opposed to the "raw" files being sent for processing. This makes any operation much faster than it would be if it were being performed sequentially...much like an octopus would make lemonade much faster than you would.

The map subtask consists in finding the relevant data by using several mathematical tricks, such as sorting, searching, indexing, and combining data into smaller, more manageable chunks of data. It can turn a whole file into a map-type object. In other words, everything is baked into key-value pairs. For instance, a text file containing the sentence "I really really really love cold cold lemonade" would be mapped into the following key-value pairs: (I, 1), (really, 3), (love, 1), (cold, 2), (lemonade, 1). The key is the mapped word and the value is the number of occurrences. This would then be the input for the reduce task, which would apply the search conditions and decide if this file is relevant for the query. In our example, it would be because we're looking for files containing the word "lemonade."

I won't go into great detail, but you can (and should) write your own Java classes (Hadoop is Java-based, even though you can use other programming languages for parts of the framework) to perform these "map" and "reduce" tasks. There's an optional "combine" task, which takes the output of the "map" task and further processes it to facilitate the work of the "reduce" task. If you are familiar with Java and want to learn more about this algorithm's implementation in Hadoop, Apache offers a great tutorial about the topic here.

So Much More

This is a bird's-eye view of the Hadoop framework, one of the main tools for processing Big Data. But there are more things you can do, more tools to explore, and more ways to use big datasets! Things like Machine Learning, Artificial Intelligence, and so on are becoming more and more mainstream and making their way from the academic to the business world. It's a brand-new field that you should explore!

Rafael Victoria-Pereira

Rafael Victória-Pereira has more than 20 years of IBM i experience as a programmer, analyst, and manager. Over that period, he has been an active voice in the IBM i community, encouraging and helping programmers transition to ILE and free-format RPG. Rafael has written more than 100 technical articles about topics ranging from interfaces (the topic for his first book, Flexible Input, Dazzling Output with IBM i) to modern RPG and SQL in his popular RPG Academy and SQL 101 series on mcpressonline.com and in his books Evolve Your RPG Coding and SQL for IBM i: A Database Modernization Guide. Rafael writes in an easy-to-read, practical style that is highly popular with his audience of IBM technology professionals.

Rafael is the Deputy IT Director - Infrastructures and Services at the Luis Simões Group in Portugal. His areas of expertise include programming in the IBM i native languages (RPG, CL, and DB2 SQL) and in "modern" programming languages, such as Java, C#, and Python, as well as project management and consultancy.

MC Press books written by Rafael Victória-Pereira available now on the MC Press Bookstore.

Evolve Your RPG Coding: Move from OPM to ILE...and Beyond Evolve Your RPG Coding: Move from OPM to ILE...and Beyond
Transition to modern RPG programming with this step-by-step guide through ILE and free-format RPG, SQL, and modernization techniques.
List Price $79.95

Now On Sale

Flexible Input, Dazzling Output with IBM i Flexible Input, Dazzling Output with IBM i
Uncover easier, more flexible ways to get data into your system, plus some methods for exporting and presenting the vital business data it contains.
List Price $79.95

Now On Sale

SQL for IBM i: A Database Modernization Guide SQL for IBM i: A Database Modernization Guide
Learn how to use SQL’s capabilities to modernize and enhance your IBM i database.
List Price $79.95

Now On Sale



Support MC Press Online

$0.00 Raised:

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: