We just talked about it.
Right now, master node needs to save some metadata information in FS and each node which has a primary shard will copy data directly to the filesystem.
That's the reason each master node and data node needs to have access to the file system.
One option could be in the future to copy all data over the wire to master node and the stream data to FS. So only master node will need to have access to the FS repository.
But it's not here yet and we need to think about it as it can come with some implications.
May be a SSH repository could be easier in that case and won't overload master node with tons of network data...
Best
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 6 mars 2014 à 18:19:43, Amit Soni (amitsoni29@gmail.com) a écrit:
Thanks David, pl do share how your discussion with Igor goes.
I agree that a "preference=local" flag will be useful since having a shared file system is just additional setup to be done and if there is any way to avoid it, things would get simpler.
-Amit.
On Wed, Mar 5, 2014 at 11:57 PM, David Pilato david@pilato.fr wrote:
In related issue:
Shared File System Repository
The shared file system repository ("type": "fs") is using shared file system to store snapshot. The path specified in the location parameter should point to the same location in the shared filesystem and be accessible on all data and master nodes.
May be we should add an option to _snapshot endpoint which could be preference=local for example which will execute the snapshot only on the local node which get the request.
Need to talk with Igor about it though to see if it makes sense or is doable.
--
David 
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 6 mars 2014 à 08:43, David Pilato david@pilato.fr a écrit :
Actually, I think that your backup file system needs to be shared on all nodes because you don't know in advance which nodes will actually perform the snapshot.
(Though I need to double check)
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 6 mars 2014 à 08:28, Amit Soni amitsoni29@gmail.com a écrit :
Thanks David. Actually "shared file system" got me a little confused with setting up a file system which would need to be mounted on all participating nodes and that seemed bizarre. Hence wanted to clarify!
-Amit.
On Wed, Mar 5, 2014 at 10:36 PM, David Pilato david@pilato.fr wrote:
It means that you can Backup on file system.
Note that it's now possible to backup to S3 and HDFS. Azure storage coming...
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 6 mars 2014 à 03:27, Amit Soni amitsoni29@gmail.com a écrit :
In the article above, it says "At the time of the initial release only shared file system repository is supported."
Can you pl clarify on this?
-Amit.
On Wed, Mar 5, 2014 at 3:38 AM, Clinton Gormley clint@traveljury.com wrote:
On 5 March 2014 12:38, Hari Prasad iamhari1234@gmail.com wrote:
So can a snapshot taken for one cluster be restored for another cluster, may be with different name?
yes
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPt3XKSb_6BshJs5rmV8efwg0iXuAQbnWOr9uR2cZfKq2%2B%3Df5g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAOGaQLUiaQekq5y_jtb%3Dr2qO9OYFHFw%3DAxamc--mDh%3Djf2Rhg%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/51072F77-AE89-41F4-9816-EDFD17B760A7%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/AF824946-2CA8-480F-906D-6134CEC4050D%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAOGaQL-sQ2Qwr2QWD%2BaUWrtWyBgYz-yU4U4Sbh%3DjEvVXT%3DRVw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.5318afd2.661e3f1e.7bfa%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/groups/opt_out.
