クラスターヘルスとモニタリング

Just like a car needs regular checks, your Elasticsearch cluster needs monitoring. This ensures it's running smoothly and efficiently.

Monitoring helps you catch problems early, before they affect your users. It's crucial to:

• Prevent data loss
• Ensure high availability
• Optimize performance
• Troubleshoot issues quickly

Elasticsearch provides a powerful REST API to check its health. The _cluster/health API is your go-to for a quick overview. It tells you if your cluster is alive and well.

You'd typically make an HTTP GET request to this endpoint:

The _cluster/health API returns a status that's typically one of three colors:

• Green: All primary and replica shards are allocated. Your cluster is fully operational.
• Yellow: All primary shards are allocated, but some replica shards are not. Data is available, but you might be at risk if a node fails.
• Red: One or more primary shards are unallocated. This means some data is unavailable. Immediate action is needed!

The _cluster/health API provides more than just a color. It shows important metrics like:

• number_of_nodes: Total nodes in the cluster.
• number_of_data_nodes: Nodes holding data.
• active_shards: Shards currently processing data.
• unassigned_shards: Shards that haven't been allocated to a node. These are often the cause of Yellow or Red status.

Always look for unassigned_shards if your status isn't Green.

Sometimes you need to check the status of individual nodes. The _cat/nodes API gives you a compact, human-readable list of all nodes, their IP addresses, roles, and resource usage.

The ?v parameter adds column headers for easier reading:

The _cat/shards API is crucial for understanding shard allocation. It lists every shard in your cluster, its index, primary/replica status, state (e.g., STARTED, UNASSIGNED), and which node it's on.

This helps diagnose Yellow or Red statuses by showing exactly which shards are unassigned:

The _cat APIs (short for 'concise and tabular') are designed for command-line use. They provide data in a plain text format, making it easy to quickly check various aspects of your cluster without parsing complex JSON.

• Human-readable output
• Fast for quick checks
• Great for scripting
• Many _cat APIs exist (e.g., _cat/indices, _cat/health)

When monitoring, keep an eye on:

• Red Cluster Status: Indicates data loss or inaccessibility.
• Yellow Cluster Status: Replica shards unassigned, risk of data loss on node failure.
• High CPU/Memory Usage: A node might be overloaded.
• Disk Space: Nodes running out of disk space can cause issues.
• Unassigned Shards: Always check _cat/shards to understand why.

These are early warning signs that require attention.

While manual checks are good, for a production system, you need proactive monitoring. Tools like Kibana's Alerting, Prometheus & Grafana, or dedicated monitoring services can automatically notify you of issues.

Proactive monitoring helps you:

• Automate health checks
• Get instant notifications
• Visualize trends over time
• Integrate with incident management

You've learned about Elasticsearch cluster health statuses. Let's test your knowledge!

We've covered essential tools for monitoring your Elasticsearch cluster:

• The _cluster/health API gives a quick overview (Green, Yellow, Red statuses).
• _cat/nodes helps you check individual node status and resources.
• _cat/shards is key to understanding shard allocation and diagnosing unassigned shards.

Regular monitoring and understanding these statuses are crucial for a stable and reliable Elasticsearch deployment.