OpenSearch data-node disk usage is rising and search latency is increasing.
Inspect shard and JVM state before deciding whether to expand capacity.
Which monitoring approach is most appropriate?
Correlate cluster health, disk, JVM pressure, shard state, and search latency before changing the domain.
Detailed explanation
Result count does not reveal disk pressure, queueing, or JVM exhaustion.
Result count does not reveal disk pressure, queueing, or JVM exhaustion.
Correlated node, index, and resource signals help isolate the cause of the degradation.
Correlated node, index, and resource signals help isolate the cause of the degradation.
API volume is not a direct measure of disk or JVM usage.
API volume is not a direct measure of disk or JVM usage.
S3 lifecycle rules do not manage OpenSearch shards.
S3 lifecycle rules do not manage OpenSearch shards.
Check official documentation
Compare the following points with the official documentation.
Amazon OpenSearch Service CloudWatch metrics、cluster health、shardsの公式説明を確認する。
What to confirm
検索結果の業務指標とクラスタリソース指標の違いを説明できる。
Key points
- Cluster health
- FreeStorageSpace
- JVM memory
- Shard
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Capacity planning
Growth, replicas, shard size, and retention determine future storage needs.
Preventive alerting
Disk pressure, JVM pressure, and unassigned shards should alert before an outage.