Could not able to take the snapshot

Elastic Stack Elasticsearch
1

{"error":{"root_cause":[{"type":"repository_verification_exception","reason":"[logs_backup] [gJSWaV3wROeSjpuYh23AFw, 'RemoteTransportException[[node-3][server3:9300][internal:admin/repository/verify]]; nested: RepositoryVerificationException[[logs_backup] a file written by master to the store [/home/vagrant/elasticsearch/backups] cannot be accessed on the node [{node-3}{gJSWaV3wROeSjpuYh23AFw}{server3}{server3:9300}]. This might indicate that the store [/home/vagrant/elasticsearch/backups] is not shared between this node and the master node or that permissions on the store don't allow reading files written by the master node];'], [flA8q0AWTjKAkTYIn0GaMw, 'RemoteTransportException[[node-2][server2:9300][internal:admin/repository/verify]]; nested: RepositoryVerificationException[[logs_backup] a file written by master to the store [/home/vagrant/elasticsearch/backups] cannot be accessed on the node [{node-2}{flA8q0AWTjKAkTYIn0GaMw}{server2}{server2:9300}]. This might indicate that the store [/home/vagrant/elasticsearch/backups] is not shared between this node and the master node or that permissions on the store don't allow reading files written by the master node];']]"}],"type":"repository_verification_exception","reason":"[logs_backup] [gJSWaV3wROeSjpuYh23AFw, 'RemoteTransportException[[node-3][server3:9300][internal:admin/repository/verify]]; nested: RepositoryVerificationException[[logs_backup] a file written by master to the store [/home/vagrant/elasticsearch/backups] cannot be accessed on the node [{node-3}{gJSWaV3wROeSjpuYh23AFw}{node3}{node3:9300}]. This might indicate that the store [/home/vagrant/elasticsearch/backups] is not shared between this node and the master node or that permissions on the store don't allow reading files written by the master node];'], [flA8q0AWTjKAkTYIn0GaMw, 'RemoteTransportException[[node-2][server2:9300][internal:admin/repository/verify]]; nested: RepositoryVerificationException[[logs_backup] a file written by master to the store [/home/vagrant/elasticsearch/backups] cannot be accessed on the node [{node-2}{flA8q0AWTjKAkTYIn0GaMw}{}{server2:9300}]. This might indicate that the store [/home/vagrant/elasticsearch/backups] is not shared between this node and the master node or that permissions on the store don't allow reading files written by the master node];']]"},"status":500}

2

You need to take the snapshot to networked storage that can be read and written to by all nodes via the same path. Elasticsearch tests this by having one node write a file and another then read it, which seems to be failing in your case.

3

Any documentation to create snapshot using curator and keep it into S3 bucket.

5

@naresh_career399,

Yes, you can follow the below link to create snapshot using curator.

https://www.elastic.co/guide/en/elasticsearch/client/curator/5.4/snapshot.html

And you can also use below snapshot template to create snapshot action file.

action: snapshot
description: >-
  Snapshot selected indices to 'repository' with the snapshot name or name
  pattern in 'name'.  Use all other options as assigned
options:
  repository: ...
  #Leaving name blank will result in the default 'curator-%Y%m%d%H%M%S'
  name:
  wait_for_completion: True
  max_wait: 3600
  wait_interval: 10
filters:
-filtertype: ...

And to keep it into s3 bucket use below link:
https://www.elastic.co/guide/en/elasticsearch/plugins/6.3/repository-s3.html

Thanks.

6

file need share stroge as nfs ..

7

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