Elastic 7.7.0 too many requests with one request!

I am developing an application using elasticsearch 7.7.0 image from docker (docker.elastic.co/elasticsearch/elasticsearch:7.7.0) with single node. Configs:

  - cluster.name=log
  - bootstrap.memory_lock=true
  - "ES_JAVA_OPTS=-Xms512M -Xmx512M"
  - discovery.type=single-node

I am using python low-level lib (elasticsearch>=7.0.0,<8.0.0) trying to post one message to an index. I am getting the error:

    Not possible to ingest text event on ElasticSearch. An exception of type TransportError occurred.
    Traceback (most recent call last):
    File "[__init__.py](http://__init__.py)", line 218, in text
    MESSENGER_NAME, bot_id, user, channel, message_text
    File "/[app/monitoring.py](http://app/monitoring.py)", line 33, in doc_ingest_autoid
    res = ES.index(index=INDEXNAME, body=doc)
    File "/usr/local/lib/python3.7/site-packages/elasticsearch/client/utils.py", line 92, in _wrapped
    return func(*args, params=params, headers=headers, **kwargs)
    File "/usr/local/lib/python3.7/site-packages/elasticsearch/client/__init__.py", line 411, in index
    File "/usr/local/lib/python3.7/site-packages/elasticsearch/transport.py", line 362, in perform_request
    File "/usr/local/lib/python3.7/site-packages/elasticsearch/connection/http_urllib3.py", line 252, in perform_request
    self._raise_error(response.status, raw_data)
    File "/usr/local/lib/python3.7/site-packages/elasticsearch/connection/base.py", line 282, in _raise_error
    status_code, error_message, additional_info
    elasticsearch.exceptions.TransportError: TransportError(429, 'cluster_block_exception', 'index [bots] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];')

Do you have any idea why could this be happening?

This block means that your disks are too full, so yes one indexing request is indeed too many requests. The server logs should also be telling you this in more detail. This will resolve itself once you have deleted some data to bring your disks under 90% capacity.

Uou, that message isn't clear at all. There is no mention to my disk being full (but it is really). I will try to clean it up and do new tests again.

Just to close the topic. The problem was indeed the high disk usage despite the message not being that helpful.

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