Updated: Beware of a Long Message
Before moving to a large server, I want to understand what is wrong with this.
This is the elasticsearch server MVP in AWS (EC2). Two microspheres with a size of only 600 mb each.
I want to understand what happened to this configuration. As you can see, there is a bottleneck in the main team. The operating memory is full, the heap memory is still low, and although the processor processor is operating at its maximum, the system CPU is low.
I reduced the complexity of each document in mass mailing and set an unwanted field so as not to be indexed. The screenshots below are my last attempt.
Is this an I / O bottleneck? I store data in an S3 bucket.
Server Information:
2 ( ), 3 , 1 . , node . " " node .
, , , :
:
Primary
( ):
5 :
( )
( ):
py-elasticsearch, . , , :
elasticsearch.exceptions.ConnectionError:
ConnectionError(HTTPConnectionPool(host='IP_HERE', port=9200):
Read timed out. (read timeout=10)) caused by:
ReadTimeoutError(HTTPConnectionPool(host='IP_HERE', port=9200):
Read timed out. (read timeout=10))
" ". 20, , refresh , .
- , (CPU, RAM, Disk, Network...) .