Guess which book, as yet unreleased, is pre-selling at #1 in Amazon’s “Corruption & Misconduct in Politics” category?
P.S., I possibly may earn a few helpful cents as an Amazon affiliate bookseller if you follow this link to the book. But only if you actually buy it or something else. Otherwise, bupkis. No soup for me. Thanks for considering.
Now more than ever, with some 40 million Americans unemployed, the nation’s economy stalled by protests and a deadly pandemic, and federal leadership failing, we need to review and draw again from hard lessons learned during major events in our nation’s labor history.
Mike Stout’s well-written new memoir, Homestead Steel Mill: The Final Ten Years, should be a must-read for labor leaders, labor activists, labor academics, labor lawyers, and labor specialists at all levels of local, state, and federal government. It deserves attention as well from libraries and general readers interested in American labor history, how unions operate, and what roles unions will play in the nation’s difficult economic recovery.
The author has walked the walk of a Pittsburgh area blue-collar steelworker and union leader. Stout’s credits are too numerous to summarize here, but include writing for and editing an influential union newspaper, helping found one of the first and largest union food banks, and organizing several community coalitions aimed at trying to help save steel mill jobs. He also is known internationally as a labor and social activist, as well as singer-songwriter.
The Homestead steelworks already had earned a prominent and disturbing place in American labor history when Mike Stout began working there for U.S. Steel in 1978 as a utility crane operator. Indeed, as one of his well-researched book’s sources, Brett Reigh, has noted in a master’s thesis: “In its 106 years of operation, the Homestead Works [had] witnessed some of the greatest battles ever waged between labor and capital in the United States.”
In 1892, for example, disputes between the Amalgamated Association of Iron and Steel Workers and the Carnegie Steel Company exploded into a lockout and then the infamous “Homestead Massacre” that claimed at numerous lives. In an attempt to break the union, Carnegie’s leaders had brought in some 300 Pinkerton guards to try to overwhelm the strikers. A violent battle ensued, and some strikers and Pinkerton guards died. The Pinkertons eventually surrendered, but the strike ended after 6,000 troops from Pennsylvania’s state militia arrived, sided with the mill’s management, and stood guard while strikebreakers were brought in to replace union workers.
Working at Homestead
Mike Stout was one of some 7,000 employees at Homestead and believed he had found a job for life in one of America’s most essential industries. His area also had several other U.S. Steel mills and a total of about 30,000 steelworkers.
In a chapter titled “Homestead–Forge of the Universe, Heart of Industrial Unionism,” Stout recounts some of the Homestead mill’s historical significance:
“Homestead, Pennsylvania, has been synonymous with steelmaking since 1880. For over one hundred years, the Homestead mill, seven miles southeast of downtown Pittsburgh on the south side of the Monongahela River, made the steel that helped shape the Industrial Revolution in America, producing armor plate during America’s involvement in both world wars, as well as the Korean and Vietnam Wars. It made structural beams for skyscrapers, including the St. Louis Arch, the Home Life Insurance Building in Chicago, the Pan Am, Empire State, Rockefeller Center, and United Nations Buildings in New York City, and the shafting for the power plant at the Hoover Dam. It made the steel for every major bridge and waterway back in the day, from the Panama Canal through the Golden Gate and Oakland Bay Bridges in San Francisco out west to the George Washington and Verrazano-Narrows Bridges back east.”
During Stout’s times at Homestead, however, steel mill owners were refusing to modernize and increasingly sending jobs and steel investments to cheaper sites overseas. Many workers, including Stout, were laid off repeatedly and not all were called back to work. As Homestead’s workforce shrank, union leaders and union members continued battling to maintain jobs and benefits and to keep employees as safe as possible in dangerous working conditions.
How dangerous? According to Stout:
“Working in a steel mill was dangerous beyond description. You worked in extreme temperatures. Heavy equipment and machinery were flying all about you. You could be working in front of rolling red hot steel where the temperature in the front of your body was 2,300 degrees, but your back would be freezing. You worked a different time shift every week, working 8:00 a.m. to 4:00 p.m., then 4:00 p.m. to midnight the following week, then midnight to 8:00 a.m. the third week. Also, every week your two days off would change; you’d be off Sunday and Monday, then the next week Monday and Tuesday, etc. Your entire life outside of work was determined by your life in the mill. There wasn’t much time or energy for anything else.”
Union members and leaders also fought among themselves over what was the right balance of “union democracy,” how trade unions are governed–an important focus in Stout’s new book. A key concern of the rank and file (the union members) was that union executives would accurately represent the members’ interests when dealing with, and negotiating with, mills’ executives. Much of Stout’s memoir is devoted to his time navigating and leading some of the inner workings of union activities, politics, and activism. Many readers who have no experience with unions may find these chapters both eye-opening and surprisingly engrossing.
After the plant was shut down in 1987, a shopping mall was built on its site. In a review of Stout’s book, written by a former steelworker at a nearby mill, Mark Fallon recalls: “The union at the Homestead mill, United Steelworkers (USW) Local 1397 and its Rank and File Caucus, was an ‘insurgent’ local that often took vigorous issue with the policies not only of U.S. Steel, but those of its parent United Steelworkers of America International union.”
Fallon adds that while Stout served as the union’s “Grievance Chair for the entire mill between 1981-1987,” he won a significant victory for more than 3,000 former workers: more than $12 million in back pay, severance pay, pensions, and unemployment benefits. “He was the last union official out the door when the mill closed and stayed on for another four years fighting for workers’ pay and rights without receiving a dime from the union.”
After Homestead, What Lies Ahead?
The future of work in America is frighteningly uncertain as this review is being written. In the ongoing pandemic, millions have lost their jobs, businesses, and even careers, while millions of others are now working from home with no certainty that they will have workplaces, positions, or employers to return to in the future.
As Charles McCollester emphasizes in the foreword to Stout’s book: “The coming generation of workers faces a radically changing world of artificial intelligence, robots, drones, pervasive surveillance, genetic engineering, insidious pollution, and accelerating climate change. Mike’s account of a grassroots democratic labor insurgency fighting for economic survival remains relevant, even as the nature of work changes.” (McCollester is former chief steward, UE Local 610, Switch and Signal plant and former professor of Labor Relations at Indiana University of Pennsylvania.)
Stout hopes to see a future where disparate groups unite and create a larger and more powerful social and political force. He urges: “There is commonality in all movements out there—be it Black Lives Matter, the #MeToo women’s movement, health care, immigration rights, worker rights, the environmental movement, or the movements against the many unjust wars our government is waging. Everyone needs a decent job, reasonable benefits, a democratic voice, a healthy environment, equal treatment, dignity, and a peaceful life. Until organized labor joins in a sustained coalition with these movements as one voice, as well as with our elected representatives, we will remain isolated, picked off one by one.”
How to Get the Book
To purchase the book, contact: PM Press, Oakland, CA. www.pmpress.org $24.95 (paperback), $60 (hard cover), $8.95 (ebook) + shipping & handling. For a signed, First Edition copy at a discount price, contact the author at: firstname.lastname@example.org $25 (soft cover) including shipping and handling $40 (hard cover) including shipping and handling.
Staying Sane & Entertained While Forced to Hide from the Coronavirus
Charles Dickens likely did not have a deadly global pandemic in mind when he wrote the “best of times, worst of times” opening for his novel, A Tale of Two Cities. He was contrasting life in profitable, peaceful London with grim life in revolution-torn Paris at the end of the 18th century.
With most Americans now being told to stay away from their jobs and remain sheltered for weeks in their homes or apartments, people are coming face-to-face with a harsh reality: How do we keep ourselves sane and entertained while contained within four walls almost around the clock?
What follows are short reports from five people in different parts of the United States. They describe how they have responded thus far to being confined to quarters. They have not complained of feeling like people under house arrest or like space passengers practicing for a long, mundane cruise to Mars.
For some, at least, the pandemic response has been a time for reflection and reinvention, as well as frequently seeking and needing entertainment.
Erin J., a Boston college student, is still recovering from coronavirus-like symptoms. She has been staying in a small living space for several weeks since her university closed and put its classes online.
“Well, I wasn’t tested for it, but I can say that the first week I slept for 16 hours a day and didn’t care much for entertainment. I’d put on anything to have noise. The second week was a little better, but I still slept most of the day and night but had midterm exams to prepare for. Took me four days to write a paragraph. I started consuming more media as a means to stay distracted and try to figure out what was going on. I found movies that were like comfort food and almost played them on loop. By about the end of the second week I started feeling human [again] and was more interested in doing schoolwork, and became more aware that I was stuck inside.
“I’ve stayed entertained by trying to find comfort in media that reminds me of the world I knew.”
Terry P., a writer and entertainer in Long Island, N.Y., has chosen a positive andpragmatic approach to coping with the current economic and health disaster:
“Planted a bunch of seeds and ordered a compost bin, planning a vegetable garden. Also taking piano lessons and writing a book for self-employed entertainers about how to kick start their businesses when this all ends. And watching Netflix, of course.”
Linda B. is a PRN (pro re nata – “as the situation demands”) worker in Austin, Texas, who currently is not doing much work, but filling time with many other activities.
“Slowly reading a serious book, What the Eyes Don’t See, about the Flint water crisis, by the pediatrician and activist who didn’t stop until the story was told and changes made. Making bread for my neighbors. Cooking new recipes. Using FaceTime, learning Zoom and What’sApp to see and talk to people I love. Staying up-to-date on happenings for my work which doesn’t need an ‘as needed’ PRN employee right now. Walking with another neighbor or [doing] something for exercise most days. Learning what it feels like to see the world “non-24″ by going to bed when I feel like it and staying there 7-8 hours no matter what hour that is. Today, 6 am – 3 pm. Recording the local news in case I’m doing something more fulfilling at the time; then watching without ads. Doing the same with movies and documentaries so that when I choose to watch TV, I can see interesting things or delete it. Learning after three weeks that I can live without touch for today. I may crack tomorrow, but for today, I’m at peace working on the ‘Mindboggler 1000 piece jigsaw puzzle of the Carpathian Mountains’ I picked up on a whim at Half Price Books months ago.”
Musician and retired teacher Pamela F. lives in a small-ish town north of Austin, Texas, and avoids boredom by staying active on several fronts:
“Walking twice a day. Sometimes walking with the seven-year-old son of my next-door, single-parent neighbor. Trying to learn Zoom. Writing music. Using FaceTime and Facebook Messenger to see friends and relatives. Eating, and then eating some more. Small projects like cleaning out a drawer or a closet. Napping. Continuing my physical therapy regimen. Playing piano and accordion. Keeping up with friends on Facebook. Reading. Quiet time.”
Joe S., a Dallas-area journalist, is taking a more focused approach to using his sheltering-at-home time:
That’s a 547-page work of history subtitled “A Saga of Churchill, Family, and Defiance During the Blitz.” Sounds appropriate and inspiring for coping with current times.
Catherine B., an Austin, Texas, university librarian (her school has gone to online classes) also is focusing on a central task, but is taking breaks to pursue other, more entertaining activities:
“I have been reading manuals and a glossary for a new integrated library system, the thing behind the scene that runs the online catalog. In my free time, I am sewing quilt blocks. I got excited when I found the perfect elastic for making masks. [And] Tom and I watched ‘Downton Abbey,’ the series and the movie, on DVD. We started that in early March before the social distancing. I have also made 20-second videos of rain and birds singing.”
Many things can be done while stuck indoors, including taking online classes, watching yoga or tai chi how-to videos, reading books previously ignored on your bookshelves, starting a home-based business, baking bread, or taking up new or lapsed hobbies. The possibilities are vast, and the time to get started currently is abundant.
Thanks for reading this effort to make creative use of some of my own inside time. And please feel free to add comments. Something posted here may someday end up in somebody’s sociology book, history book, graduate thesis, movie, or novel about these treacherous times. Who knows?
Si Dunn is an Austin, Texas, novelist, screenwriter, book reviewer, and journalist. His books include Dark Signals, Jump, and Erwin’s Law.
Reinventing a city does not have to start from the top down. You don’t need big government initiatives and huge funding, this noteworthy book contends.
People within America’s growing “Maker culture” can rework and improve a local economy. They can bring needed and worthwhile changes to a city’s culture using significantly smaller budgets and much less government intervention. And the reinvigoration can happen in small, rural towns as well as in large metropolitan areas, the authors of Maker City believe.
What, exactly, is Maker culture? Here’s how it is defined in this book:
“Today’s Makers are crafters, artists and artisans, technologists, hobbyists, amateur scientists, entrepreneurs, engineers, woodworkers, roboticists, and many others. They are young people engaging in hands-on projects that introduce them to science and technology in creative ways. Makers are also adults who see themselves as inventors and experimentalists. Some have PhDs and others are self-educated. Makers are practicing a craft or challenging themselves to learn a new hobby. They are creative problem-solvers who gain the confidence that they can tackle ever-larger problems.”
The movement brings the local “best and brightest” together with other Makers around the globe, linked together via the Internet or in person as solutions to problems are sought, made and tested.
A key tenet of city-level Maker culture is “Open Innovation, the idea that the best solutions do not lie with any one individual or institution inside city government but must be created through collaboration and engagement that looks outside for answers and examples of what to do to affect change.”
The notion of city reinvention typically puts spotlights on big cities where factories and industries have been lost and large buildings and neighborhoods have fallen into ruin. For example, efforts to find a major new role, such as commercial shipyard, for the old Brooklyn Navy Yard repeatedly failed, until a new, Maker-oriented approach was tried. That’s when the Brooklyn Navy Yard “started to make a comeback as a community housing many smaller businesses made up of Makers, artists, artisans, and manufacturing concerns. Today over 330 businesses and 7,000 people work out of the Brooklyn Navy Yard in 3.5 million square feet growing to 5.0 million square feet by 2018,” Maker City reports.
Small towns also can benefit from Maker innovation and talent, the book emphasizes. Ways can be found to take advantage of local history and draw visitors, as well as new residents. Old, unused buildings can be upgraded to emphasize and celebrate local history and serve as meeting centers or performance sites. Other buildings can be converted to innovation centers and incubators that give local residents places or other help to start businesses and hire other local residents.
The book is well-written and well-organized and offers a wide range of ideas, case studies and trend reports. For example, big assembly line jobs are not coming back, unless robots provide the “labor.” But small-scale manufacturing is expanding, thanks to 3D printers and other devices and innovations. Small-scale manufacturers also are often selling their products directly to customers from their sites. And customers are showing a stronger preference for buying locally made products.
Whether you work in business, government, science or education or are simply concerned about urban renewal, Maker City deserves careful consideration.
The three authors of this book note that “[d]ata science is a very wide field, so wide indeed that a book ten times the size of this one wouldn’t be able to cover it all. For each chapter, we picked a different aspect we find interesting. Some hard decisions had to be made to keep this book from collapsing your bookshelf!”
In their decisions and selections, they have made some good choices. Introducing Data Science is well written and generally well-organized (unless you are overly impatient to get to hands-on tasks).
The book appears to be aimed primarily at individual computer users and persons contemplating possible careers in data science–not those already working in, or heading, big data centers. The book also could be good for managers and others trying to wrap their heads around some data science techniques that could help them cope with swelling mountains of business data.
With this book in hand, you may be impatient to open it to the first chapter and dive headfirst into slicing, dicing, and graphing data. Try to curb your enthusiasm for a little while. Books from Manning generally avoid the “jump in now, swim later” approach. Instead, you get some overviews, explanations and theory first. Then you start getting to the heart of the matter. Some like this approach, while others get impatient with it.
In Introducing Data Science, your “First steps in big data” start happening in chapter five, after you’ve first delved into the data science process: 1. Setting the research goal; 2. Retrieving data; 3. Data preparation, 4. Data exploration; 5. Data modeling; and 6. Presentation and automation.
The “First steps” chapter also is preceded by chapters on machine learning and how to handle large data files on a single computer.
Once you get to Chapter 5, however, your “First steps” start moving pretty quickly. You are shown how to work (at the sandbox level) with two big data applications, Hadoop and Spark. And you get examples of how even Python can be used to write big data jobs.
From there, you march on to (1) the use of NoSQL databases and graph databases, (2) text mining and text analytics, and (3) data visualization and creating a small data science application.
It should be noted and emphasized, however, that the concluding pages of chapter 1 do present “An introductory working example of Hadoop.” The authors explain how to run “a small [Hadoop] application in a big data context,” using a Hortonworks Sandbox image inside a VirtualBox.
It’s not grand, but it is a start in a book that otherwise would take four chapters to get to the first hands-on part.
Near the beginning of their book, the authors also include a worthy quote from Morpheus in “The Matrix”: “I can only show you the door. You’re the one that has to walk through it.”
This book can be a good entry door to the huge and rapidly changing field of data science, if you are willing to go through it and do the work it presents.
I strolled into my favorite Austin Starbucks recently and noticed a startling sight. Every person standing in line or sitting at tables simultaneously had their head down as if in group prayer. All at the same moment were staring at their smartphones.
I pulled out my own phone, dramatically flipped it open, held it aloft, and waved it in silent protest. No one got the joke, because no one noticed.
We’ve all seen people become panic-stricken and helpless when they realize they have lost or forgotten their “smart” device, or had it stolen. “Everything—my whole life—is on there!” one friend wailed recently. “All my pictures, my personal information, my contacts. And—oh, god–work emails! I don’t know what to do!” She kept frantically digging through her big purse, which also contained “everything,” including papers from work, so she could keep working at home after she got off work. When I called her phone from my phone, we found her “smart” phone buried deep beneath makeup containers and assorted other purse rubble.
Many people now use their smartphones for “everything,” from paying a restaurant check (after using the calculator function to split it and calculate the tip) to hailing an Uber ride and remotely controlling their home air conditioning. And, anytime a question is raised in a group, several people will circumvent natural debate or brainstorming by immediately going to Google and reading off some article titles and paragraphs.
Meanwhile, a few unrelated videos also will pop up and be shared: Cat attacks python! Man sets shoes on fire by standing on hot coals! Ha-ha-ha!
The smartphone video distractions are only going to get worse. As AT&T’s CEO, Randall Stephenson recently told Fortune magazine: “…mobile video…is the real deal,” adding: “Half our mobile network traffic is video now, and it’s really growing fast.”
So, recent statutes banning talking or texting on a digital device while driving are now far behind the curve of progress. (“Sorry, officer, I was not breaking the law. I was watching Game of Thrones while paying no attention to the traffic and scenery around me.”)
Perhaps it is time to ask yourself two serious questions. Are you losing touch with the real world as you become increasingly distracted by your smartphone? And will your growing dependence on its “smart”-ness make you correspondingly “dumb” over time?
Get this book, whether you are new to working with Big Data or now an old hand at dealing with Big Data’s seemingly never-ending (and steadily expanding) complexities.
You may not agree with all that the authors offer or contend in this well-written “theory” text. But Nathan Marz’s Lambda Architecture is well worth serious consideration, especially if you are now trying to come up with more reliable and more efficient approaches to processing and mining Big Data. The writers’ explanations of some of the power, problems, and possibilities of Big Data are among the clearest and best I have read.
“More than 30,000 gigabytes of data are generated every second, and the rate of data creation is only accelerating,” Marz and Warren point out.
Thus, previous “solutions” for working with Big Data are now getting overwhelmed, not only by the sheer volume of information pouring in but by greater system complexities and failures of overworked hardware that now plague many outmoded systems.
The authors have structured their book to show “how to approach building a solution to any Big Data problem. The principles you’ll learn hold true regardless of the tooling in the current landscape, and you can use these principles to rigorously choose what tools are appropriate for your application.” In other words, they write, you will “learn how to fish, not just how to use a particular fishing rod.”
Marz’s Lambda Architecture also is at the heart of Big Data, the book. It is, the two authors explain, “an architecture that takes advantage of clustered hardware along with new tools designed specifically to capture and analyze web-scale data. It describes a scalable, easy-to-understand approach to Big Data systems that can be built and run by a small team.”
The Lambda Architecture has three layers: the batch layer, the serving layer, and the speed layer.
Not surprisingly, the book likewise is divided into three parts, each focusing on one of the layers:
In Part 1, chapters 4 through 9 deal with various aspects of the batch layer, such as building a batch layer from end to end and implementing an example batch layer.
Part 2 has two chapters that zero in on the serving layer. “The serving layer consists of databases that index and serve the results of the batch layer,” the writers explain. “Part 2 is short because databases that don’t require random writes are extraordinarily simple.”
In Part 3, chapters 12 through 17 explore and explain the Lambda Architecture’s speed layer, which “compensates for the high latency of the batch layer to enable up-to-date results for queries.”
Marz and Warren contend that “[t]he benefits of data systems built using the Lambda Architecture go beyond just scaling. Because your system will be able to handle much larger amounts of data, you’ll be able to collect even more data and get more value out of it. Increasing the amount and types of data you store will lead to more opportunities to mine your data, produce analytics, and build new applications.”
This book requires no previous experience with large-scale data analysis, nor with NoSQL tools. However, it helps to be somewhat familiar with traditional databases. Nathan Marz is the creator of Apache Storm and originator of the Lambda Architecture. James Warren is an analytics architect with a background in machine learning and scientific computing.
If you think the Big Data world already is too much with us, just stick around a while. Soon, it may involve almost every aspect of our lives.
It likewise helps to understand how CSVs (Comma Separated Values) can be used. And you should know how to set up and run local web servers on your computer. Prior knowledge of D3.js and SVG (Scalable Vector Graphics) is not necessary, however.
Some reviewers have remarked on the amount of how-to and technical information packed into DS3.js in Action. It is indeed impressive. And, yes, it really can seem like concepts, details and examples are being squirted at you from a fire hose, particularly if you are attempting to race through the text. As Elijah Meeks writes, “[T]he focus of this book is on a more exhaustive explanation of key principles of the library.”
So plan to take your time. Tackle D3.js in small bites, using the d3js.org website and this text. I am pretty new to learning data visualization, and I definitely had never heard of visualizations such as Voronoi diagrams, nor tools such as TopoJSON, until I started working my way through this book. And those are just a few of the available possibilities.
I have not yet tried all of the code examples. But the ones I have tested have worked very well, and they have gotten me thinking about how I can adapt them to use in some of my work.
I am a bit disappointed that the book takes 40 pages to get to the requisite “Hello, world” examples. And once you arrive, the explanations likely will seem a bit murky and incomplete to some readers.
I really wish I had had this book when I started a 14-year career in software development and testing. I was hired back in the days when you could get a software job by having a college degree (in anything), a couple of positive references and some decent writing skills. If you could also turn on a computer and bring up the DOS prompt, so much the better.
No matter how many skills you actually had, you were going to spend a couple of months learning your new environment and your new job, while also attending free, company-sponsored training classes (during working hours). Meanwhile, if you had any questions, you could just go ask the C guru down the hall or dour Mister Assembler, who lived in the big, corner cubicle and seemed to have no other life.
I am retired now from the corporate world of software. And when, out of curiosity, I look at today’s help-wanted postings for developers and testers, I am stunned by how much knowledge, training and verifiable skills one person is expected to bring to the table. At least ten jobs, it seems, have been rolled into one.
For that reason and more, I highly recommend Soft Skills by John Z. Sonmez. He believes, he says, in taking “a holistic approach to software development. This means that I think that if you want to be a better software developer—a better anything, really—you need to focus on the entire person, not just one or two areas of your life.”
Sonmez offers up a wealth of how-to information and useful advice covering everything from “hacking” a job interview to developing a personal brand and staying physically fit in a job that requires long hours sitting on one’s butt. He also offers tips for learning new things quickly, staying productive (using a modified version of the Pomodoro Technique)–and investing part of your paycheck so you can retire early or at least have a comfortable cushion if you get laid off and decide to become an independent consultant.
Yes, there is a lot of common advice sense in Soft Skills–the kind of advice you likely have heard before but ignored. Still, Sonmez’s book makes clear, compelling cases for why you really do have to watch out for–and take care of–yourself these days. You seemingly can’t count on an employer to do much of anything anymore, except view you as a unit of cost to be reduced or eliminated as soon as possible.
“Most software developers starting out in their careers make a few huge mistakes,” Sonmez writes. “The biggest of those mistakes, by far, is not treating their software development career as a business. Don’t be fooled; when you set out into the world to write code for a living, you’re no different than the blacksmith of old times setting up shop in a medieval town. Times may have changed, and most of us work for a company, but our skills and our trade belong to us and we can always choose to set up shop somewhere else. This kind of mindset is crucial to managing your career, because when you start to think of yourself as a business, you start to make good business decisions.”
This is a mindset I wish I had acquired and expanded when I got my first job in software and then began to surf the periodic waves of layoffs. If you are new at working in software development or still trying to get your foot in the door, you can get some very good information and guidance from this book. The same goes if your career currently is floundering and needs a reboot. Don’t just hit CTRL-ALT-DEL and go storming out the door. Try reading some of Sonmez’s chapters first–and at least have your resume reworked by experts who can help you boost your personal “brand.”
The explosive growth and use of Big Data in business, government, science and other arenas has fueled a strong demand for new Hadoop administrators. The administrators’ key duty is to set up and maintain Hadoop clusters that help process and analyze massive amounts of information.
New Hadoop administrators and those looking to join their ranks especially will want to give good consideration to The Cloudera Administration Handbook by Rohit Menon. This is a well-organized, well-written and solidly illustrated guide to building and maintaining large Apache Hadoop clusters using Cloudera Manager and CDH5.
The author has an extensive computer science background and is a Cloudera Certified Apache Hadoop Developer. He notes that “Cloudera Inc., is a Palo Alto-based American enterprise software company that provides Apache Hadoop-based software, support and services, and training to data-driven enterprises. It is often referred to as the commercial Hadoop company.”
CDH, Menon points out, is the easy shorthand name for a rather awkward software title: “Cloudera’s Distribution Including Apache Hadoop.” CDH is “an enterprise-level distribution including Apache Hadoop and several components of its ecosystem such as Apache Hive, Apache Avro, HBase, and many more. CDH is 100 percent open source,” Menon writes.
The Cloudera Manager, meanwhile, “is a web-browser-based administration tool to manage Apache Hadoop clusters. It is the centralized command center to operate the entire cluster from a single interface. Using Cloudera Manager, the administrator gets visibility for each and every component in the cluster.”
The Cloudera Manager is not explored until nearly halfway into the book, and some may wish it had been explained sooner, since they may be trying to learn it on day one of their new job. However, Menon wants readers first to become familiar with “all the steps and operations needed to set up a cluster via the command line” at a terminal. And these are, of course, important considerations to becoming an effective, knowledgeable and versatile Hadoop Administrator. (You may not always have access to Cloudera Manager while setting up or troubleshooting a cluster.)
The book’s nine chapters show its well-focused range:
Chapter 1: Getting Started with Apache Hadoop
Chapter 2: HDFS and MapReduce
Chapter 3: Cloudera’s Distribution Including Apache Hadoop
Chapter 4: Exploring HDFS Federation and Its High Availability
Chapter 5: Using Cloudera Manager
Chapter 6: Implementing Security Using Kerberos
Chapter 7: Managing an Apache Hadoop Cluster
Chapter 8: Cluster Monitoring Using Events and Alerts
Chapter 9: Configuring Backups
You will have to bring some hardware and software experience and skills to the table, of course. Apache Hadoop primarily is run on Linux. “So having good Linux skills such as monitoring, troubleshooting, configuration, and security is a must” for a Hadoop administrator, Menon points out. Another requirement is being able to work comfortably with the Java Virtual Machine (JVM) and understand Java exceptions.
But those skills and his Cloudera Administration Handbook can take you from “the very basics of Hadoop” to taking up “the responsibilities of a Hadoop administrator and…managing huge Hadoop clusters.”