深入理解HBase：HBase.in.Action实战

5星 · 超过95%的资源需积分: 10 145 浏览量更新于2024-07-26 3 收藏 5.67MB PDF 举报

"HBase.in.Action.pdf" 《HBase in Action》是由Nick Dimiduk和Amandeep Khurana合著的一本关于Apache HBase的专业书籍，由Manning Publications出版。这本书深入浅出地介绍了HBase，一个基于Google Bigtable理念设计的开源分布式数据库，它属于Apache Hadoop生态系统的一部分，特别适合处理海量、半结构化的数据。本书的前言由Michael Stack撰写，他可能是HBase社区的重要成员或贡献者。书中内容涵盖了HBase的基础知识，如其设计理念、架构和工作原理，以及如何在实际项目中部署和管理HBase。技术编辑Mark Henry Ryan确保了书中技术信息的准确性和专业性。书中可能包含以下关键知识点： 1. **HBase概述**：HBase是一个NoSQL数据库，采用列族模型，支持实时读写，具有高可扩展性和容错性，适合大数据场景。 2. **HBase架构**：包括Master节点、RegionServer、Zookeeper的角色，以及HDFS（Hadoop分布式文件系统）是如何与HBase协同工作的。 3. **数据模型**：解释行、列族、列和时间戳的概念，以及它们如何组合成HBase中的数据结构。 4. **操作HBase**：如何创建表、插入和查询数据，以及进行数据的过滤和排序。 5. **HBase的分布式特性**：如何自动分区（Region分裂）、负载均衡，以及如何处理节点故障。 6. **性能优化**：包括读写性能调优策略，例如预加载、批量写入和索引的使用。 7. **监控和运维**：如何监控HBase集群的健康状态，以及问题排查和故障修复的方法。 8. **应用案例**：展示了HBase在实际业务中的应用场景，如互联网日志分析、实时推荐系统等。 9. **与其他Hadoop组件集成**：如与Hadoop MapReduce、Hive、Pig等的集成，以及如何在HBase上构建复杂的数据处理管道。 10. **最佳实践**：提供了关于设计模式、数据模型选择和系统架构方面的建议，帮助读者避免常见错误。此书对于希望理解和使用HBase的开发者、数据工程师以及对大数据存储感兴趣的读者来说是一份宝贵的资源。通过阅读，读者不仅可以掌握HBase的基础知识，还能学习到如何在生产环境中有效地使用和管理HBase集群。

preface

I got my start with

ase in the fall of 2008. It was a young project then, released only

in the preceding year. As early releases go, it was quite capable, although not without its

fair share of embarrassing warts. Not bad for an Apache subproject with fewer than 10

active committers to its name! That was the height of the No

SQL

hype. The term No

SQL

hadn’t even been presented yet but would come into common parlance over the next

year. No one could articulate why the idea was important—only that it was important—

and everyone in the open source data community was obsessed with this concept. The

community was polarized, with people either bashing relational databases for their fool-

ish rigidity or mocking these new technologies for their lack of sophistication.

The people exploring this new idea were mostly in internet companies, and I came

to work for such a company—a startup interested in the analysis of social media con-

tent. Facebook still enforced its privacy policies then, and Twitter wasn’t big enough to

know what a Fail Whale was yet. Our interest at the time was mostly in blogs. I left a

company where I’d spent the better part of three years working on a hierarchical data-

base engine. We made extensive use of Berkeley

, so I was familiar with data tech-

nologies that didn’t have a

SQL

engine. I joined a small team tasked with building a

new data-management platform. We had an

SQL

database stuffed to the gills with

blog posts and comments. When our daily analysis jobs breached the 18-hour mark,

we knew the current system’s days were numbered.

After cataloging a basic set of requirements, we set out to find a new data technol-

ogy. We were a small team and spent months evaluating different options while main-

taining current systems. We experimented with different approaches and learned

PREFACE

xvi

firsthand the pains of manually partitioning data. We studied the

CAP

theorem and

eventual consistency—and the tradeoffs. Despite its warts, we decided on

ase, and

we convinced our manager that the potential benefits outweighed the risks he saw in

open source technology.

I’d played a bit with Hadoop at home but had never written a real MapReduce job.

I’d heard of

ase but wasn’t particularly interested in it until I was in this new posi-

tion. With the clock ticking, there was nothing to do but jump in. We scrounged up a

couple of spare machines and a bit of rack, and then we were off and running. It was a

NET

shop, and we had no operational help, so we learned to combine bash with rsync

and managed the cluster ourselves.

I joined the mailing lists and the

IRC

channel and started asking questions. Around

this time, I met Amandeep. He was working on his master’s thesis, hacking up

ase

to run on systems other than Hadoop. Soon he finished school, joined Amazon, and

moved to Seattle. We were among the very few HBase-ers in this extremely Microsoft-

centric city. Fast-forward another two years…

The idea of

ase in Action was first proposed to us in the fall of 2010. From my

perspective, the project was laughable. Why should we, two community members,

write a book about

ase? Internally, it’s a complex beast. The Definitive Guide was still

a work in progress, but we both knew its author, a committer, and were well aware of

the challenge before him. From the outside, I thought it’s just a “simple key-value

store.” The

API

has only five concepts, none of which is complex. We weren’t going to

write another internals book, and I wasn’t convinced there was enough going on from

the application developer’s perspective to justify an entire book.

We started brainstorming the project, and it quickly became clear that I was wrong.

Not only was there enough material for a user’s guide, but our position as community

members made us ideal candidates to write such a book. We set out to catalogue the

useful bits of knowledge we’d each accumulated over the couple of years we’d used

the technology. That effort—this book—is the distillation of our eight years of com-

bined

ase experience. It’s targeted to those brand new to

ase, and it provides

guidance over the stumbling blocks we encountered during our own journeys. We’ve

collected and codified as much as we could of the tribal knowledge floating around

the community. Wherever possible, we prefer concrete direction to vague advice. Far

more than a simple

FAQ

, we hope you’ll find this book to be a complete manual to

getting off the ground with

ase.

ase is now stabilizing. Most of the warts we encountered when we began with the

project have been cleaned up, patched, or completely re-architected.

ase is

approaching its 1.0 release, and we’re proud to be part of this community as we

approach this milestone. We’re proud to present this manuscript to the community in

hopes that it will encourage and enable the next generation of HBase users. The sin-

gle strongest component of

ase is its thriving community—we hope you’ll join us in

that community and help it continue to innovate in this new era of data systems.

ICK

IMIDUK

PREFACE

xvii

If you’re reading this, you’re presumably interested in knowing how I got involved

with

ase. Let me start by saying thank you for choosing this book as your means to

learn about

ase and how to build applications that use

ase as their underlying

storage system. I hope you’ll find the text useful and learn some neat tricks that will

help you build better applications and enable you to succeed.

I was pursuing graduate studies in computer science at

Santa Cruz, specializing

in distributed systems, when I started working at Cisco as a part-time researcher. The

team I was working with was trying to build a data-integration framework that could

integrate, index, and allow exploration of data residing in hundreds of heterogeneous

data stores, including but not limited to large

RDBMS

systems. We started looking for

systems and solutions that would help us solve the problems at hand. We evaluated

many different systems, from object databases to graph databases, and we considered

building a custom distributed data-storage layer backed by Berkeley

. It was clear

that one of the key requirements was scalability, and we didn’t want to build a full-

fledged distributed system. If you’re in a situation where you think you need to build

out a custom distributed database or file system, think again—try to see if an existing

solution can solve part of your problem.

Following that principle, we decided that building out a new system wasn’t the best

approach and to use an existing technology instead. That was when I started playing

with the Hadoop ecosystem, getting my hands dirty with the different components in

the stack and going on to build a proof-of-concept for the data-integration system on

top of

ase. It actually worked and scaled well!

ase was well-suited to the problem,

but these were young projects at the time—and one of the things that ensured our

success was the community.

ase has one of the most welcoming and vibrant open

source communities; it was much smaller at the time, but the key principles were the

same then as now.

The data-integration project later became my master’s thesis. The project used

ase at its core, and I became more involved with the community as I built it out. I

asked questions, and, with time, answered questions others asked, on both the mailing

lists and the

IRC

channel. This is when I met Nick and got to know what he was work-

ing on. With each day that I worked on this project, my interest and love for the tech-

nology and the open source community grew, and I wanted to stay involved.

After finishing grad school, I joined Amazon in Seattle to work on back-end distrib-

uted systems projects. Much of my time was spent with the Elastic MapReduce team,

building the first versions of their hosted

ase offering. Nick also lived in Seattle,

and we met often and talked about the projects we were working on. Toward the end

of 2010, the idea of writing HBase in Action for Manning came up. We initially scoffed

at the thought of writing a book on

ase, and I remember saying to Nick, “It’s gets,

puts, and scans—there’s not a lot more to

ase from the client side. Do you want to

write a book about three

API

calls?”

But the more we thought about this, the more we realized that building applications

with

ase was challenging and there wasn’t enough material to help people get off the

剩余361页未读，继续阅读

Mushroom_lb

粉丝: 149

深入理解HBase：HBase.in.Action实战

《HBase in Action(中文)》: HBase入门指南

HBase实战：清晰英文PDF版

HBase实战指南：从入门到精通

HBase实战(HBase In Action)

浅谈HBASE数据结构设计.pdf

Hadoop_in_Action.pdf

Hadoop权威指南中文版（第二版）+Hadoop in Action

HBase实战指南：大数据技术详解

HBase应用构建与部署实践指南

Hadoop实战官方PDF：Chuck Lam著

最新资源