Roadmap for "Stateless" Elasticsearch

I read yesterday's blog post about the future of a "stateless" Elasticsearch architecture, where one of the big benefits is the ability to scale indexing workloads separately from search workloads...

I have a 30+ node Elastic cluster that ingests (and deletes) 6 billion records every day, and it’s been a constant struggle to keep the indexing workload from interfering with search performance. So the new architecture sounds like EXACTLY what we need.

Do you have a rough idea of the release timeline?

While we appreciate there is a tonne of excitement around this topic, we don't publish release timelines sorry to say :slight_smile:

Okay... How about a slightly different question.

Is this the pre-launch announcement of Elasticsearch 9?


I haven't heard anything, so I would say no.

The way I read the blog post, this may be a dedicated future Elastic Cloud feature as that is mentioned in several places.

I read it the same way, it looks like it will be a Elastic Cloud only feature.

Since it will rely in a search model similar to searchable snapshots, if it lands in the self-managed version it will probably be on the Enterprise license.

Or maybe this could be seen as a hint that Elastic will focus on the cloud offering and the self-managed version will lack some features in the future.

1 Like

I think this idea is kind of interesting, from a high-level architecture overview, it seems very similar to: thanos, which has shown the feasibility of this type of architecture (even as user deployable).

One thing I'd be curious about, are the intended use cases for this new architecture. The blog post doesn't really state the exact use-cases this setup is intended for but seems to imply that its mainly for logs/metrics/append-only style use-cases.

I'd also be interested in seeing the searching side benchmarks. While the indexing improvements are pretty significant, it would be interesting to know if there are any trade-offs for the searching side.

1 Like

I'm curious about where this will leave on-prem customers. It's currently less expensive for my organization to run Elastic on servers we maintain. This could potentially change costs enough to make a difference for us.

Watching hopefully.

From me point of view, the high availability and data replication / horizontal scaling is a must-have no matter what the architecture is.
I am curious to see how this would be adressed based on the simple architecture diagram here: Stateless — your new state of find with Elasticsearch | Elastic Blog

If all these criteria are met and the respons time / speed is improved, this would be perfect.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.