Wait for seq no refreshed timed out – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.9-8.9

Briefly, this error occurs when Elasticsearch is unable to refresh the sequence number within the specified timeout period. This could be due to heavy indexing load, slow disk I/O, or network latency. To resolve this issue, you can increase the timeout value, reduce the indexing load, optimize your disk I/O operations, or improve your network connectivity. Additionally, ensure your Elasticsearch cluster is properly sized and configured for your workload.

This guide will help you check for common problems that cause the log ” Wait for seq_no [{}] refreshed timed out [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.

Log Context

Log “Wait for seq_no [{}] refreshed timed out [{}]” class name is SearchService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // index shard on timeout so that a timed-out listener does not use up any listener slots.
 final TimeValue timeout = request.getWaitForCheckpointsTimeout();
 final Scheduler.ScheduledCancellable timeoutTask = NO_TIMEOUT.equals(timeout) ? null : threadPool.schedule(() -> {
 if (isDone.compareAndSet(false; true)) {
 new ElasticsearchTimeoutException("Wait for seq_no [{}] refreshed timed out [{}]"; waitForCheckpoint; timeout)
 }; timeout; Names.SAME);  // allow waiting for not-yet-issued sequence number if shard isn't promotable to primary and the timeout is less than or equal


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?