ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #elasticsearch
Upgrade sequencing decision We run a Kibana instance connected to a self-managed Elasticsearch cluster, both currently on the same minor version of a recent 8.x release. Elastic's documentation states that Kibana and Elasticsearch are expected to run matching versions, with only narrow exceptions during rolling upgrades, and that Kibana newer than Elasticsea
When configuring node-to-node communication in Elasticsearch (version 8.x), the xpack.security.transport.ssl.verification_mode setting determines how certificates are validated during the SSL handshake. The goal is to maintain a secure transport layer while allowing the cluster to scale across dynamic infrastructure where hostnames may change or be assigned
Before optimizing an Elasticsearch cluster, I need to confirm where the indexing bottleneck resides. I plan to query the nodes stats API for metrics such as indexing_pressure, thread_pool queue sizes, and merge throttling times, while also sampling hot threads to see CPU contention. However, I am unsure which combination of these metrics most reliably indica
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
Goal: Ensure continuous pagination using search_after when the primary sort field may contain duplicate values across documents, without encountering errors that halt scrolling. Constraint/uncertainty: Documentation states that the sort field must be unique per document; duplicates cause an error, but it is unclear whether Elasticsearch automatically incorpo
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
kibana