[Feature Request] Suspend a river

[dadoonet]

As writen in the mailing list : http://elasticsearch-users.115913.n3.nabble.com/Suspend-a-CouchDB-river-tp2964592p2964592.html

It’s not possible to suspend a CouchDB river without deleting it.
If I delete it, I will have to restart it from scratch.
By suspending it, I will be able to restart the river from the last sequence number given by _changes API.

Thanks,
David.

[max-mapper]

+1

[dadoonet]

Hi,

I have seen that curl -XPOST 'localhost:9200/_river/_close' seems to suspend the river.
To restart it, I have only to do curl -XPOST 'localhost:9200/_river/_open'

So, I suggest to close this issue and I will add a pull request on elasticsearch.github.com to document this.

Agree ?

Thanks

[Andrewsville]

Doesn't it suspend ALL rivers in the cluster? That might not be exactly what you want.

[dadoonet]

@Andrewsville : sure. But I have only one river at this time. So it works.

[tommymonk]

+1

[spinscale]

Just as a side note. If you want this feature, simply implement it in your river. Most rivers are built similar and use a an indexer and a slurper thread. Before doing anything inside the slurper thread, recheck the configuration by getting it from the _river index and check for a enabled/disabled boolean, which might have been set while the thread was sleeping. Did that for all my rivers in order to disable getting data from flaky sources or when doing administration work on those systems.

No need for getting this natively into ES.