# FS River not working in elasticsearch cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [May 23, 2013, 8:58am UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089 "2013-05-23T08:58:29Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![imdhmd](https://avatars.discourse-cdn.com/v4/letter/i/d07c76/32.png) [@imdhmd](https://discuss.elastic.co/u/imdhmd)\ **Post date:** [May 23, 2013, 8:58am UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/1 "2013-05-23T08:58:29Z")
I am using: - FS River version: 0.0.3 - Elasticsearch: 0.20.6 Setup: - Two nodes of elasticsearch in a cluster, _es-one_ & _es-two_ - A local file system on _es-one_ at /tmp/data - A remotely mounted (via fuse-sshfs) file system on _es-two_ at /tmp/data SCENARIO 1: Issued the following rest call to create fsriver: curl -XPUT es-one:9200/\_river/data-river/\_meta -d '{ "type": "fs", "fs": { "url": "/tmp/data", "update\_rate": 120000 }, "index": { "index": "data", "type": "doc", "bulk\_size": 50 } }' Expectation: - River with name [data-river] should be created - All files under _/tmp/data_ should be indexed Actual: - [data-river] wasn't created - Expected files didn't get indexed SCENARIO 2: After SCENARIO-1, I brought down elasticsearch server at es-two. Then, - [data-river] got created - all expected files got indexed Question: For FS river to get created and start indexing, do we require to have only one node running in the cluster? Thanks, Imdad/Vidhi -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [May 23, 2013, 11:08am UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/2 "2013-05-23T11:08:32Z")
Did you install the FSRiver plugin on both nodes and restart them both? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 23 mai 2013 à 10:58, Imdad Ahmed [imdhmd@gmail.com](mailto:imdhmd@gmail.com) a écrit : > I am using: > > - FS River version: 0.0.3 > - Elasticsearch: 0.20.6 > > Setup: > > - Two nodes of elasticsearch in a cluster, es-one & es-two > - A local file system on es-one at /tmp/data > - A remotely mounted (via fuse-sshfs) file system on es-two at /tmp/data > > SCENARIO 1: > Issued the following rest call to create fsriver: > curl -XPUT es-one:9200/\_river/data-river/\_meta -d '{ > "type": "fs", > "fs": { > "url": "/tmp/data", > "update\_rate": 120000 > }, > "index": { > "index": "data", > "type": "doc", > "bulk\_size": 50 > } > }' > > Expectation: > > - River with name [data-river] should be created > - All files under /tmp/data should be indexed > > Actual: > > - [data-river] wasn't created > - Expected files didn't get indexed > > SCENARIO 2: > After SCENARIO-1, I brought down elasticsearch server at es-two. > Then, > > - [data-river] got created > - all expected files got indexed > > Question: > For FS river to get created and start indexing, do we require to have only one node running in the cluster? > > Thanks, > Imdad/Vidhi > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![imdhmd](https://avatars.discourse-cdn.com/v4/letter/i/d07c76/32.png) [@imdhmd](https://discuss.elastic.co/u/imdhmd)\ **Post date:** [August 23, 2013, 8:35am UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/3 "2013-08-23T08:35:39Z")
This is a late reply to this thread, to bring it to closure. Yes, Pilato, we did follow the correct steps. But the problem was something else. Elasticsearch user on es-two didnt have proper access to /tmp/data. Once we corrected accessibility issue, this problem no longer occured. On Thursday, May 23, 2013 4:38:32 PM UTC+5:30, David Pilato wrote: > Did you install the FSRiver plugin on both nodes and restart them both? > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 23 mai 2013 à 10:58, Imdad Ahmed \<[imd...@gmail.com](mailto:imd...@gmail.com) \\> a > écrit : > > I am using: > > - FS River version: 0.0.3 > - Elasticsearch: 0.20.6 > > Setup: > > - Two nodes of elasticsearch in a cluster, _es-one_ & _es-two_ > - A local file system on _es-one_ at /tmp/data > - A remotely mounted (via fuse-sshfs) file system on _es-two_ at /tmp/data > > SCENARIO 1: > Issued the following rest call to create fsriver: > curl -XPUT es-one:9200/\_river/data-river/\_meta -d '{ > "type": "fs", > "fs": { > "url": "/tmp/data", > "update\_rate": 120000 > }, > "index": { > "index": "data", > "type": "doc", > "bulk\_size": 50 > } > }' > > Expectation: > > - River with name [data-river] should be created > - All files under _/tmp/data_ should be indexed > > Actual: > > - [data-river] wasn't created > - Expected files didn't get indexed > > SCENARIO 2: > After SCENARIO-1, I brought down elasticsearch server at es-two. > Then, > > - [data-river] got created > - all expected files got indexed > > Question: > For FS river to get created and start indexing, do we require to have only > one node running in the cluster? > > Thanks, > Imdad/Vidhi > > -- > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 23, 2013, 8:36am UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/4 "2013-08-23T08:36:38Z")
Thanks for the feedback. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 23 août 2013 à 10:35, Imdad Ahmed [imdhmd@gmail.com](mailto:imdhmd@gmail.com) a écrit : > This is a late reply to this thread, to bring it to closure. > > Yes, Pilato, we did follow the correct steps. But the problem was something else. > Elasticsearch user on es-two didnt have proper access to /tmp/data. > Once we corrected accessibility issue, this problem no longer occured. > > On Thursday, May 23, 2013 4:38:32 PM UTC+5:30, David Pilato wrote: > Did you install the FSRiver plugin on both nodes and restart them both? > > -- > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) > @dadoonet | @elasticsearchfr | @scrutmydocs > > Le 23 mai 2013 à 10:58, Imdad Ahmed [imd...@gmail.com](mailto:imd...@gmail.com) a écrit : > > > I am using: > > > > - FS River version: 0.0.3 > > - Elasticsearch: 0.20.6 > > > > Setup: > > > > - Two nodes of elasticsearch in a cluster, es-one & es-two > > - A local file system on es-one at /tmp/data > > - A remotely mounted (via fuse-sshfs) file system on es-two at /tmp/data > > > > SCENARIO 1: > > Issued the following rest call to create fsriver: > > curl -XPUT es-one:9200/\_river/data-river/\_meta -d '{ > > "type": "fs", > > "fs": { > > "url": "/tmp/data", > > "update\_rate": 120000 > > }, > > "index": { > > "index": "data", > > "type": "doc", > > "bulk\_size": 50 > > } > > }' > > > > Expectation: > > > > - River with name [data-river] should be created > > - All files under /tmp/data should be indexed > > > > Actual: > > > > - [data-river] wasn't created > > - Expected files didn't get indexed > > > > SCENARIO 2: > > After SCENARIO-1, I brought down elasticsearch server at es-two. > > Then, > > > > - [data-river] got created > > - all expected files got indexed > > > > Question: > > For FS river to get created and start indexing, do we require to have only one node running in the cluster? > > > > Thanks, > > Imdad/Vidhi > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jamai\_Ali](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jamai\_Ali](https://discuss.elastic.co/u/jamai_Ali)\ **Post date:** [April 16, 2016, 12:20pm UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/5 "2016-04-16T12:20:48Z")
Stp j utilise fs river pour indexer des journaux sur lesquels j px mener une recherche sur le contenu ultérieurement . Apres une annee je me suis trouver avec un problem que elastic n indec plus leq nouveaux doc ou accuse un grand retard pour le faire je compte sur votre aide ---
**Author:** ![jamai\_Ali](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jamai\_Ali](https://discuss.elastic.co/u/jamai_Ali)\ **Post date:** [April 16, 2016, 12:21pm UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/6 "2016-04-16T12:21:44Z")
Juste une precision un noeud un cluster ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 16, 2016, 12:35pm UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/7 "2016-04-16T12:35:04Z")
Please use english here. There is a dedicated French area. Also don't hijack old threads and create your own. You can also open an issue in the project. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:58pm UTC](https://discuss.elastic.co/t/fs-river-not-working-in-elasticsearch-cluster/12089/8 "2017-07-05T22:58:49Z")