Elasticsearch Timeout Error After Upgrade

If you get timeout error after the Elasticsearch upgrade to above 8.3 version, it is possible that you hit this issue. Elasticsearch Timeout Error After Upgrade is known issue for the post upgrade process.


1- systemctl start elasticsearch
2- Cluster is allocating shards, and cluster status is green
3- But systemctl commands don’t give any output and waiting 4-5 minutes.
4- After this period, systemctl commands failed because of time out error.

test01$ dzdo systemctl start elasticsearch
Job for elasticsearch.service failed because a timeout was exceeded.
See “systemctl status elasticsearch.service” and “journalctl -xe” for details.

● elasticsearch.service – Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: timeout) since Sat 2023-07-22 11:33:20 +03; 16s ago
Docs: https://www.elastic.co
Process: 83851 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid –quiet (code=exited, status=143)
Main PID: 83851 (code=exited, status=143)


Add the following parameter in your system file (/usr/lib/systemd/system/elasticsearch.service)



Elasticsearch should be notifying Systemd while it starts up about its liveness, but if NotifyAccess is not present in the service file, those notifications might not be allowed to get to Systemd.
Systemd will behave like Elasticsearch is stuck and stops the Elasticsearch process.

Latest posts by Veysel YUKSEL (see all)


RDBMS ve NoSQL veri tabanı yönetimi ve Big Data teknolojileri.

You may also like...

Bir cevap yazın

E-posta hesabınız yayımlanmayacak. Gerekli alanlar * ile işaretlenmişlerdir