Knowledge of the Availability Zone and AWS Availability Zone Replicas

Question

I have some questions regarding AWS elasticsearch availability zone replicas and replicas:

• As far as I understand, in the event of a zone failure / node, if the skulls were replicated between nodes, the cluster will be able to fully recover, and I will have a whole copy of the data in each zone, is this correct?

• According to AWS elasticsearch documentation, I have to use the Amazon elasticsearch API to replicate data for an Amazon elasticsearch cluster over nodes in availability zones. But I could not find a way to configure replicas through the Amazon elasticsearch API, so I think through the Elastic API, right?

• What is the best practice for distributing a node cluster across two availability zones in the same sa-east1 region, how many dedicated master instances and data nodes should be sufficient to switch to another resource, at least to start a new environment? 2 dedicated wizards and 2 data nodes should be sufficient to prevent data loss and downtime in case of failure? I assume that 1 replica should be configured for the index. I also thought about 2-3 dedicated wizards and 3 data nodes and 2 replicas for each index.

• There is no settings file in AWS elasticsearch, the only way to change the number of replicas is using the flexible API, but I can not find a way to change the default setting, when the new index created the number of replica skulls 1, which by default matters, there is a way to change the default settings for every new index?

something like this only changes the current indices.

curl -XPUT 'https://search-aa1-a3qlyghdz2i6wszffnv4iz5cyi.sa-east-1.es.amazonaws.com/_all/_settings' -d '
{
    "index" : {
        "number_of_replicas" : 2
    }
}'

Run code

http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-managedomains.html

Thanks for any help you can provide!

Answer 1

Here are some answers to your questions.

First of all, I disclose information, I am an employee of Elastic and work on the Found team.

, / node, , , , ?

. shard , shard 0, 0, node .

, AWS ES . , . "" 30 .

AWS elasticsearch, API Amazon elasticsearch Amazon elasticsearch . API Amazon elasticsearch, , , Elastic API,??//

, 100%, AWS ES API, , API AWS ES, ES API.

Elasticsearch, ES API https://www.elastic.co/guide/en/elasticsearch/guide/current/replica-shards.html, https://www.elastic.co/guide/en/elasticsearch/reference/current/allocation-awareness.html.

"" , , , . , .

node sa-east1, , , ? 2 2 ? , 1 . 2-3 3 2 .

node 2 , AZ, node, . AWS (http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-createupdatedomains.html#es-createdomains-configure-cluster) -, , . , - 3 (1 AZ 1 , ) 4 (2 AZ), 1 .

, Found . , HA SA-East-1, Found 2 AZ ( ), master node, Found, , - / . https://www.elastic.co/blog/found-elasticsearch-in-production#networking .

AWS elasticsearch , - API, , - 1, , ?

, Elastic, - 1 . 1 , , https://www.elastic.co/guide/en/elasticsearch/guide/current/replica-shards.html#_balancing_load_with_replicas.

, , , https://www.elastic.co/guide/en/elasticsearch/guide/current/index-templates.html

Elastic Found, https://www.elastic.co/found https://www.elastic.co/found-elasticsearch-as-a-service-with-alerts