root@ip-205-2-177:~# /usr/share/elasticsearch/bin/elasticsearch -version
Version: 5.2.2, Build: f9d9b74/2017-02-24T17:26:45.835Z, JVM: 1.8.0_73
root@ip-205-2-177:~#
My ES cluster is up and running fine. I want validate the snapshot to S3. Hence as per the steps mentioned in
https://www.elastic.co/guide/en/elasticsearch/plugins/5.2/repository-s3.html , I downloaded the repository-s3-5.2.2.zip file and installed with the command (as root user)
==>> /usr/share/elasticsearch/bin/elasticsearch-plugin install file:///root/repository-s3-5.2.2.zip
The below command works fine:
PUT _snapshot/emmo_elasticsearch_backup_data_dev_region?verify=false
{
"type": "s3",
"settings": {
"bucket": "emmo-elasticsearch-backup-data-dev",
"region": "us-east",
"server_side_encryption": true
}
}
The below command returns name of all master nodes (2) and data nodes (3)
POST /_snapshot/emmo_elasticsearch_backup_data_dev_region/_verify
My elasticasearch.yml
root@ip-205-2-177:~# cat /etc/elasticsearch/elasticsearch.yml
cluster.name: horiz_dev_escluster1
node.name: 10.205.2.177
node.master: false
node.data: true
node.ingest: true
bootstrap.memory_lock: true
network.host: 127.0.0.1,10.205.2.177
http.port: 8089
bootstrap.seccomp: false
discovery.zen.ping.unicast.hosts: [ elastic-m-dev1-nd1-e.clouddqt.capitalone.com,elastic-m-dev1-nd2-e.clouddqt.capitalone.com,elastic-m-dev1-nd3-e.clouddqt.capitalone.com ]
discovery.zen.minimum_master_nodes: 2
discovery.zen.master_election.ignore_non_master_pings: true
discovery.zen.fd.ping_timeout: 120s
action.destructive_requires_name: true
cluster.routing.allocation.same_shard.host: true
indices.fielddata.cache.size: 20%
indices.breaker.fielddata.limit: 30%
indices.breaker.request.limit: 30%
cluster.routing.allocation.cluster_concurrent_rebalance: 4
thread_pool.bulk.queue_size: 5000
discovery.zen.ping_timeout: 6s
discovery.zen.commit_timeout: 60s
path.data: /opt/elasticsearch
path.repo: /opt/elasticsearch
My EC2 instance as IAM ROLE with FULL S3 access. From AWS CLI, I'm able to upload the file from the ES instances. All the below commands works from Ec2 instances..
aws s3 ls
aws s3 cp aaa.txt s3://
When execute the snapcommand PUT command which is mentioned above,
the log indicates PUT is success.. but after few lines..its says HEAD on the same path and says 404 (Not Found)..