1

I am getting that exception when view category in front end , I did re index also.

[2023-11-09T05:26:45.393702+00:00] report.CRITICAL: Elasticsearch\Common\Exceptions\ServerErrorResponseException: {"error":{"root_cause": [{"type":"no_shard_available_action_exception","reason":null,"index_uuid":"WJLPjai1SamDpLoyR_gerA","shard":"0","index":"intro-uat_product_1_v3"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"intro-uat_product_1_v3","node":null,"reason":{"type":"no_shard_available_action_exception","reason":null,"index_uuid":"WJLPjai1SamDpLoyR_gerA","shard":"0","index":"intro-uat_product_1_v3"}}]},"status":503} in /var/www/html/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:726

2
  • Have you checked elasticsearch status on server side ? Commented Nov 9, 2023 at 7:23
  • I think it may be an elasticsearch version issue. Please try to update your elasticsearch version See the following document for Magento 2 system requirements including Elasticsearch. devdocs.magento.com/guides/v2.4/install-gde/… Commented Nov 17, 2023 at 5:08

2 Answers 2

0

This may be your elastic search having an issue. please purge elastic search and reinstall maybe after that, it will work using the below command.

first, try to restart elastic search service using this command

sudo systemctl restart elasticsearch

After running this command issue still happened then purge and reinstall it.

sudo apt-get remove --purge elasticsearch
sudo rm -rf /etc/elasticsearch
sudo rm -rf /var/lib/elasticsearch

sudo apt-get install elasticsearch={install latest version}
sudo systemctl start elasticsearch
curl http://localhost:9200/
0

I ran into this issue, and the issue was that the server reached 85% of used space.

The default config prevent new shards being allocated to a node in this condition (https://www.elastic.co/guide/en/elasticsearch/reference/2.4/disk-allocator.html) :

Controls the low watermark for disk usage. It defaults to 85%, meaning ES will not allocate new shards to nodes once they have more than 85% disk used. It can also be set to an absolute byte value (like 500mb) to prevent ES from allocating shards if less than the configured amount of space is available.

I found the solution here with a similar "no_shard_available_action_exception" issue.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.