# Does elasticsearch contain a "run now" feature?

**URL:** <https://discuss.elastic.co/t/does-elasticsearch-contain-a-run-now-feature/13880>\
**Category:** Elasticsearch\
**Created:** [October 8, 2013, 7:46pm UTC](https://discuss.elastic.co/t/does-elasticsearch-contain-a-run-now-feature/13880 "2013-10-08T19:46:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://discuss.elastic.co/u/Richard)\
**Post date:** [October 8, 2013, 7:46pm UTC](https://discuss.elastic.co/t/does-elasticsearch-contain-a-run-now-feature/13880/1 "2013-10-08T19:46:20Z")

</div>

Can I run a River "on demand" or do I have to wait for it's polling time to  
expire?

--  
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).

---

<div class="post-metadata">

**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:** [October 8, 2013, 8:06pm UTC](https://discuss.elastic.co/t/does-elasticsearch-contain-a-run-now-feature/13880/2 "2013-10-08T20:06:33Z")

</div>

If you want to do that, that means you probably don't need a River but something similar to a batch I guess.

To answer to your question, I think that it first depends on the river implementation itself. In most cases, remove the river and create it again.

It should do the trick.

## HTH

David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 8 oct. 2013 à 21:46, Richard [richard.seidel@mercy.net](mailto:richard.seidel@mercy.net) a écrit :

> ## Can I run a River "on demand" or do I have to wait for it's polling time to expire?
> 
> 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).

--  
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).

---

<div class="post-metadata">

**Author:** ![sina\_tamanna](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@sina\_tamanna](https://discuss.elastic.co/u/sina_tamanna)\
**Post date:** [October 9, 2013, 6:35am UTC](https://discuss.elastic.co/t/does-elasticsearch-contain-a-run-now-feature/13880/3 "2013-10-09T06:35:48Z")

</div>

As David mentioned, it depends on the river implementation. For JDBC river  
you could use: curl -XPOST 'localhost:9200/\_river/my\_jdbc\_river/\_induce'

--  
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).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:13am UTC](https://discuss.elastic.co/t/does-elasticsearch-contain-a-run-now-feature/13880/4 "2017-07-06T02:13:14Z")

</div>

Closed on July 6, 2017, 2:13am UTC


