分片与副本详解
掌握分片用于水平扩展以及副本用于高可用性和容错的概念，了解其在 Elasticsearch 中的应用。
分片与副本详解 是 CoddyKit 上的免费 Elasticsearch & Full Text Search Systems 课时。 这是第 1 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Elasticsearch & Full Text Search Systems 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Elasticsearch & Full Text Search Systems 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Scaling Elasticsearch Data
Welcome to a crucial lesson on scaling and reliability in Elasticsearch! As your data grows, a single server might not be enough.
Today, we'll explore two fundamental concepts: Sharding and Replicas. They are essential for handling large datasets and ensuring your search service stays online.
The Data Growth Challenge
Imagine your application becomes super popular, and you're collecting millions of documents every day. A single Elasticsearch server (called a node) has limits:
- Storage Capacity: It can only hold so much data.
- Processing Power: Searching through huge amounts of data takes time.
- Single Point of Failure: If that one server goes down, your search is offline!
We need a way to distribute data and ensure constant availability.
Introducing Sharding
Sharding is how Elasticsearch handles horizontal scaling. Think of it like breaking a very large book into several smaller, independent books.
Each 'smaller book' is called a shard. When you index documents, Elasticsearch distributes them across these shards. This allows you to store more data and process queries faster by using multiple servers.
Primary Shards: Data Distribution
When you create an index, you define a certain number of primary shards. Every document you add to that index will belong to one of these primary shards.
These shards are distributed across the nodes in your Elasticsearch cluster. This means that if you have 3 primary shards and 3 nodes, each node could hold one primary shard, spreading the load.
Configuring Primary Shards
You define the number of primary shards when you create an index. Once an index is created, you cannot change the number of primary shards for it.
Here's how to create an index with 3 primary shards:
PUT /my_products_index
{
"settings": {
"number_of_shards": 3
}
}The Need for Replicas
Sharding helps with scaling, but what about reliability? If one node (and its primary shard) fails, you lose part of your data and your search service might become incomplete or unavailable.
This is where replicas come in. They are copies of your primary shards, designed to provide high availability and fault tolerance.
Replica Shards: Safety & Speed
A replica shard is an exact copy of a primary shard. If a node hosting a primary shard fails, a replica shard can be promoted to become the new primary, preventing data loss and downtime.
Replicas also serve another purpose: they can handle read requests! This means you can scale your search throughput by having multiple copies of your data ready to respond to queries.
Configuring Replica Shards
You can define the number of replica shards when creating an index, or you can change it later for an existing index. A common setup is to have 1 replica (meaning 2 copies of your data in total: 1 primary + 1 replica).
Here's how to create an index with 3 primary shards and 1 replica per primary shard:
PUT /my_products_index
{
"settings": {
"number_of_shards": 3,
"number_of_replicas": 1
}
}Shards & Replicas Together
Elasticsearch smartly distributes primary and replica shards across different nodes. This is crucial for resilience!
- A primary shard and its replicas are never placed on the same node.
- If a node fails, Elasticsearch can use a replica on another node to keep your data available.
- This setup ensures high availability and allows your cluster to continue operating even with node failures.
Quick Check
You've learned about the core concepts of sharding and replicas. Let's see if you can identify their primary roles.
Recap: Sharding & Replicas
Great job! In this lesson, we demystified sharding and replicas, two vital concepts for any robust Elasticsearch deployment.
- Sharding (primary shards) allows you to break your data into smaller pieces, enabling horizontal scaling for storage and processing.
- Replicas (replica shards) are copies of primary shards that provide fault tolerance (high availability) and boost read performance.
Together, they make your Elasticsearch cluster scalable, resilient, and performant!
常见问题解答
「分片与副本详解」课时是免费的吗？
是的 — 「分片与副本详解」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Elasticsearch & Full Text Search Systems 课程的其余内容，请升级到 CoddyKit PRO。 Elasticsearch & Full Text Search Systems 课程共包含 4 节课。
「分片与副本详解」这节课中我会学到什么？
掌握分片用于水平扩展以及副本用于高可用性和容错的概念，了解其在 Elasticsearch 中的应用。 你通过在浏览器中直接运行的动手代码来练习 Elasticsearch & Full Text Search Systems，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Elasticsearch & Full Text Search Systems 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Elasticsearch & Full Text Search Systems 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 1 节课，共 4 节。
「分片与副本详解」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Elasticsearch & Full Text Search Systems 课中编写并运行代码吗？
能。每节 Elasticsearch & Full Text Search Systems 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。