Elasticsearch database services for production teams.
JusDB provides Elasticsearch database services for scoped projects, ongoing remote DBA coverage, incident support, shard and index design, query and heap tuning, and version upgrades. Our engineers work on Elastic Cloud, on Kubernetes with ECK, and on your own servers or cloud VMs. 24x7 on-call is available under your service agreement.
Or request a free audit of one database instance. Already in an incident? See Elasticsearch support.
- NDA before access
- Read-only by default
- Changes measured against your baseline
Elasticsearch version status
Pick the version you run
Elasticsearch 9.4 and 9.5
MaintainedThe two newest 9.x minors, and the only 9.x lines that still get patch releases. Elastic released 9.5 on 4 August 2026.
Elastic maintains 9.x until at least 15 October 2027. A cluster on 9.0 to 9.3 gets no more fixes until it moves to 9.4 or 9.5.
Plan a 9.x upgradeElasticsearch 8.19
Final 8.x minorThe last 8.x minor release. Elastic maintains 8.x until 15 January 2027 and supports it until 15 July 2027.
Upgrades to 9.1 or later start from 8.19, so a cluster on an older 8.x minor moves to the latest 8.19 patch first.
Plan the move to 9.xElasticsearch 7.17
End of lifeThe last release, 7.17.29, shipped in June 2025, and Elastic support ended on 15 January 2026.
The path to 9.x runs through 8.19, and indices created in 7.x must be reindexed, deleted, or marked read-only before a 9.x node will start.
Keep 7.17 running while you upgradeVersion status from Elastic's end-of-life policy, the upgrade guide, and the Elasticsearch release notes, checked 28 October 2026.
- Platforms
- Elastic Cloud, Kubernetes with ECK, and your own servers or cloud VMs on AWS, Google Cloud, or Azure
- High availability
- Replica shards across zones, three master-eligible nodes, snapshots, and cross-cluster replication
- Incidents
- Initial-response targets are set in your service agreement. See the targets
Symptoms
Eight Elasticsearch problems we are asked to fix
Each one has a cause we can read from the cluster's own APIs and logs. The scoping call starts from the symptom you see, and the version and platform you run.
Shards stay unassigned and the cluster stays yellow or red after a node restart or a disk past the 85% low watermark, and nobody has read the allocation explain output.
Searches slow down as small shards multiply because each shard searches on a single thread, so thousands of small shards drain the search thread pool.
Bulk indexing returns 429 errors at peak when thread pool queues fill or in-flight indexing passes its default limit of 10% of the heap, and clients retry without backing off.
New fields stop documents from indexing because dynamic mapping adds a field for every new key until index.mapping.total_fields.limit, 1,000 by default, rejects the document.
Searches fail with circuit breaker errors when heap use passes the parent breaker limit, 95% of the heap by default, and nobody has traced the request behind it.
The cluster loses its master when one zone fails because two of the three master-eligible nodes run in that zone, and one node alone cannot form a quorum.
The upgrade off 7.17 or 8.x keeps slipping after Elastic support for 7.17 ended in January 2026, while maintenance for 8.x ends on 15 January 2027.
Hot nodes hold data nobody searches because no ILM policy moves older indices to the warm, cold, or frozen tiers, so retention grows on the fastest disks.
If one of these is costing your team time, a scoping call is the place to start.
Book a 30-min scoping call (opens Google Calendar in a new tab)Disk space
How a full disk turns Elasticsearch indices read-only
By default, Elasticsearch stops allocating shards to a node past 85% disk use and moves shards off it past 90%. At 95%, the flood stage, it blocks writes to every index with a shard on that node.
Three data nodes, three outcomes
Choose a state to see what happens to writes.
Ingest and index lifecycle
Shippers send bulk requests to a data stream, and ILM rolls the write index over by shard size.
Node 1
Holds the primary shards of the write index
Under 85%
Node 2
Holds their replicas
Under 85%
Node 3
Holds older indices until ILM deletes them
Under 85%
Every node has room, so replicas and relocated shards can go to any of them.
Ingest and index lifecycle
Bulk requests to any index with a shard on node 1 fail with a cluster_block_exception. Kibana can stop loading if its own system indices are blocked too.
Node 1
Past 95%, the flood stage
Indices read-only
Node 2
Past 90%, the high watermark
Takes no shards
Node 3
Past 85%, the low watermark
Takes no moved shards
Nobody was alerted as the disks filled. At flood stage, Elasticsearch set index.blocks.read_only_allow_delete on every index with a shard on node 1. Searches still run, and a whole index can still be deleted, but writes, document deletes, and metadata changes fail. Neither other node can take the shards it needs to move.
Ingest and index lifecycle
Disk alerts fire before the low watermark, and ILM moves older indices to the warm tier.
Node 1
Crossed the alert threshold first
Alert raised
Node 2
Holds replicas, under the low watermark
Takes shards
Node 3
Holds older indices, under the low watermark
Takes shards
The alert leaves time to add disk or nodes, or to shorten retention, before node 1 reaches the low watermark. If a node still reaches flood stage, the runbook frees space, and Elasticsearch lifts the block once disk use falls below the high watermark.
We size disks, shard counts, and retention together, so every data node stays under the low watermark at full retention. Alerts cover disk use per node, unassigned shards, and any index with the read-only block.
Elastic recommends its default watermarks, and we change them only when your disks call for it. On disks over 2TB, the default max_headroom settings put flood stage at 100GB free rather than at 95% use. We rehearse the recovery on a copy: freeing space, adding a node, and confirming the block lifts.
What we cover
Full-spectrum Elasticsearch engineering
From one slow search to a major upgrade: node stats, slow logs, the Profile API, and allocation explain drive each change, measured against your baseline.
Index and shard strategy
Shard counts and sizes set from your data volume and queries, with rollover sizing each index instead of one index per day.
- Shards sized to Elastic's 10GB to 50GB guidance
- Index templates with explicit mappings
- ILM rollover, data tiers, and retention
Query profiling and relevance
We read the slow logs and Profile API output for your slowest searches before changing queries, mappings, or analyzers.
- Search and indexing slow logs, which are off by default
- BM25 relevance tuning on your real queries
- Vector search on dense_vector fields with kNN
JVM and garbage collection tuning
Heap size, circuit breakers, and garbage collection read from node stats and GC logs before any setting changes.
- Elastic's automatic heap sizing, unless node stats argue for a change
- Manual heaps of at most half the RAM, below the compressed oops threshold
- Circuit breaker trips traced to the request behind them
Cross-cluster replication (CCR)
Replicas spread across zones inside each cluster. Where your Elastic subscription includes cross-region CCR, a follower cluster in a second region keeps a searchable copy if one region fails.
- Three master-eligible nodes, one per zone
- Shard allocation awareness across zones
- Read-only follower indices that pull changes from the leader
Version upgrades
Each upgrade is rehearsed on a copy with a snapshot taken first, because Elasticsearch cannot downgrade a node once an upgrade starts.
- 7.17 to 8.19, then 8.19 to 9.x
- Upgrade Assistant checks before each major version
- Moves to Elastic Cloud by snapshot and restore or reindex
Security and role-based access
Authentication, roles, and encryption reviewed against the controls your auditors ask about.
- TLS on the HTTP and transport layers
- Least-privilege roles for people, services, and API keys
- Field- and document-level security where your subscription includes it
Incident support
A critical (P1) page, answered within your agreement's target
JusDB keeps your recovery procedures (runbooks) written down, so an incident starts from a known plan instead of a blank page.
Initial-response targets
2 to 4 hours
Business hours
During covered business hours
15 minutes
24x7 on-call
P1 incidents
Production database down, primary unreachable, data corruption risk, or active failover event.
Severe latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.
Non-critical slow query regression, staging issue, backup warning, or replication check alert.
Configuration question, index advisory, planned schema review, or general operational request.
Our engineering team is in India; business-hours coverage is Mon–Fri 09:00–18:00 IST (UTC+5:30), and 24x7 on-call is available under your service agreement.
Initial-response targets, not resolution guarantees. The target for your engagement is set in your service agreement.
What happens on a P1 page
Page
You page the on-call engineer
Through the escalation path your service agreement names.
Triage
Root cause from cluster health and allocation explain
Unassigned shards, breaker trips, and rejected bulk requests traced to the node, index, or query behind them.
Mitigate
Stabilize first, from the runbook
Free disk space, cancel the runaway search, or slow the heaviest ingest, then fix the cause once the cluster is steady.
After
A review after every P1
What happened, why, and the change that stops it happening again.
Before and between incidents
- Your setup, written down firstDuring onboarding we record your versions, node roles, shard layout, ILM policies, and snapshot repositories, so an incident starts with context.
- One escalation path, in writingYour service agreement names how to reach the on-call engineer and in which hours, for each cluster it covers.
- Reviews between incidentsWe review shard counts and sizes, disk headroom against the watermarks, heap pressure, and snapshot health, and report open risks with recommended next steps.
- Version dates trackedWe track Elastic's maintenance and support dates for the Elasticsearch and ECK versions you run, and plan upgrades before maintenance ends.
Process
How an Elasticsearch engagement runs, step by step
Written findings come before any change. Your team approves production changes, except routine actions you have pre-approved.
Scoping call
Your clusters, versions, platforms, and what you need covered.
Read-only review under NDA
Our engineers use named accounts with read-only privileges, such as monitor and view_index_metadata, then read cluster settings, node stats, shard allocation, slow logs, and ILM and snapshot status.
A written report before any change
Each finding comes with the change we propose, how we will measure it, and a way to undo it (a rollback plan).
Changes, then handover
We rehearse risky changes on a snapshot-restored copy, apply them in the windows you approve, measure them against the baseline, and hand over updated operating instructions (runbooks).
Step one is a 30-minute scoping call.
Book a 30-min scoping call (opens Google Calendar in a new tab)Ways to work
Choose the Elasticsearch service your team needs
Start with the responsibility you need covered. Each engagement has its own scope, deliverables, access requirements, and acceptance criteria.
Projects
Scoped Elasticsearch projects
A defined piece of work with written findings, hands-on changes, and validation against your baseline.
- Elasticsearch consultingShard design, index lifecycle, capacity, and licensing decisions, scoped as one project.
- Migration and upgradesVersion upgrades and moves to Elastic Cloud, with a snapshot first and a rollback plan.
- Elasticsearch on KubernetesECK operator design, storage, and upgrades for clusters that run on Kubernetes.
Ongoing
Ongoing coverage and support
JusDB monitors the databases, carries out the agreed maintenance, and responds to incidents during the coverage the proposal names. The team keeps a change record, recovery procedures, and a review after every P1.
- Remote DBAMonitoring, maintenance, snapshot checks, and capacity planning for Elasticsearch under an agreed scope.
- Elasticsearch supportIncident help for a yellow or red cluster, unassigned shards, or tripped breakers, with coverage agreed before work starts.
- Managed DBA servicesOngoing coverage for your other database engines too.
Where your Elasticsearch runs, and the tools around it
Your team and ours
What a managed Elasticsearch service still leaves to your team
Managed cloud databases automate much of the infrastructure layer, but your team still owns query performance, capacity, cost, and incident decisions.
| Question | Managed cloud service | Your own servers or Kubernetes |
|---|---|---|
| Nodes, storage, and patches | Elastic runs them on Elastic Cloud Hosted. You choose when to upgrade, and a snapshot is taken first. | Your team, or JusDB under your agreement. |
| Snapshots and restores | Snapshots run automatically to the found-snapshots repository. Testing a restore is still your team's job. | Your team registers a snapshot repository and sets SLM policies, on your own servers and on ECK. |
| Shards, mappings, and ILM | Yours. Elastic runs the nodes, not your index design. | Yours. |
| Disk space and watermarks | Autoscaling can add storage to a data tier when you enable it. It does not scale back down. | Your team tracks disk use against the watermarks and adds nodes or disks in time. |
| Versions and end of life | The same Elastic end-of-life policy. You start upgrades, but Elastic can force a patch upgrade for a critical security or stability issue. | Your calendar. Maintenance for 8.x ends on 15 January 2027. |
| License terms | Set by your Elastic Cloud subscription. | Elastic's default distribution uses the Elastic License 2.0. The free parts of the source are also offered under SSPL and, since 2024, AGPLv3. |
Your team keeps control
- Set business priorities, application requirements, and release plans
- Approve production changes, except routine actions you have pre-approved
- Own your cloud accounts, access policies, and vendor relationships
- Decide when maintenance can happen and how quickly service must recover
- Move the work in-house or to another provider after your agreement's notice period, with your data returned or deleted and the transition help your agreement sets out (Terms, section 8)
JusDB handles the agreed database work
- Monitor database health, investigate alerts, and involve the right people
- Review query performance, replication, capacity, and backup health
- Carry out approved changes and update the operating instructions they affect
- Report completed work, open risks, and recommended next steps
Weighing Elastic Cloud against running Elasticsearch yourself? We compare both against your workload on a scoping call.
Book a 30-min scoping call (opens Google Calendar in a new tab)Further reading
Elasticsearch guides and a comparison
Guides from our blog on index lifecycle and on choosing a search engine, plus a comparison with OpenSearch.
Guide
Elasticsearch index management with ILM
Index settings at creation, shard sizing, ILM rollover and delete phases, force merge for older indices, and health checks.
Guide
Elasticsearch vs Typesense vs Meilisearch
Where each search engine fits, and the operating effort each one asks of your team.
Comparison
Elasticsearch vs OpenSearch
Licensing, Kibana against OpenSearch Dashboards, vector search, and managed options from Elastic and AWS.
FAQ
Common Elasticsearch questions
What buyers ask about Elasticsearch services, cluster performance, and Elastic Cloud.
Still have a question?
Ask it on a scoping call. No production access needed.
Book a 30-min scoping call (opens Google Calendar in a new tab)What Elasticsearch services do you provide?
JusDB provides Elasticsearch remote DBA coverage, incident support, and scoped projects. Projects cover shard and index design, lifecycle policies (ILM), query and heap tuning, security reviews, and version upgrades. A move from Elasticsearch to OpenSearch is scoped as a separate migration project. 24x7 on-call is available under your service agreement; without it, coverage is business hours. Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees.
How do you optimize Elasticsearch cluster performance?
JusDB starts from measurements: node stats, slow logs, thread pool rejections, and the Profile API show where time and heap go. The usual fixes are shard sizing with ILM rollover, explicit mappings, and query rewrites. Others make bulk clients back off on 429 errors, or adjust heap and circuit breaker settings. Each change is measured against your baseline before the next one.
Do you support both self-hosted and Elastic Cloud?
Yes, JusDB supports both self-managed Elasticsearch and Elastic Cloud Hosted. Self-managed covers your own servers, cloud VMs, and Kubernetes with Elastic Cloud on Kubernetes (ECK). Elastic Cloud Hosted runs on AWS, Google Cloud, and Azure. Amazon OpenSearch Service is covered on JusDB's OpenSearch page. The proposal names which deployments the engagement includes.
Next step
Talk to an Elasticsearch engineer about your databases
Tell us what is slow, fragile, or due to change. The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance, subject to availability: mutual NDA before read-only access, a prioritized report within one week after access is ready, and no obligation.
NDA before access, read-only by default, and written scope first
Compare with other databases
If you are weighing alternatives, these are the databases most often compared with this one.
OpenSearch
The Apache 2.0 fork of Elasticsearch 7.10.2, now governed under the Linux Foundation. Compare APIs, plugins, and managed options before you choose or move.
ClickHouse
A columnar database that teams compare with Elasticsearch for log and event analytics, where aggregations matter more than full-text relevance.
pgvector
Vector similarity search inside PostgreSQL, an alternative to Elasticsearch k-nearest-neighbor search when your data already lives in PostgreSQL.
PostgreSQL
Built-in full-text search with tsvector columns and GIN indexes covers simpler search needs without a separate cluster.