Real one shot jdbc river

Hi all,

we run a jdbc river once per night for a complete recreation of our index.

The river - once it has been created - will run again after a restart of
elasticsearch cluster (single node cluster). But what we try to achieve is
a one shot river, which isn't being re-run after restart of cluster.

Naturally we can trigger an event (e.g. as a cronjob) which - after the
estimated end of river run - deletes the river again. But this results in
additional efforts.

The easiest strategy may be do delete the river right away after creating
it. But I suppose in this case the running river would be stopped...?

My question is: what is the best way to create a one shot river which is
not being re-run after restart of cluster?

I noticed the oneshot strategy but didn't find any documentation
in https://github.com/jprante/elasticsearch-river-jdbc/wiki/Strategies.

Any help would be appreciated.

Regards,

Abid

--
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/d642e1ff-64a1-4ac9-b2b3-bba38b5c07e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

So I tried the oneshot strategy with no success. The river is being rerun
after restart of cluster.

Am Donnerstag, 12. Februar 2015 15:22:27 UTC+1 schrieb Abid Hussain:

Hi all,

we run a jdbc river once per night for a complete recreation of our index.

The river - once it has been created - will run again after a restart of
elasticsearch cluster (single node cluster). But what we try to achieve is
a one shot river, which isn't being re-run after restart of cluster.

Naturally we can trigger an event (e.g. as a cronjob) which - after the
estimated end of river run - deletes the river again. But this results in
additional efforts.

The easiest strategy may be do delete the river right away after creating
it. But I suppose in this case the running river would be stopped...?

My question is: what is the best way to create a one shot river which is
not being re-run after restart of cluster?

I noticed the oneshot strategy but didn't find any documentation in
https://github.com/jprante/elasticsearch-river-jdbc/wiki/Strategies.

Any help would be appreciated.

Regards,

Abid

--
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/dea5b9f2-36a5-4f09-b2c0-ca44157a4d9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yes, a river instance is restarted by ES automatically at node restart. You
must delete it after work is done in order to free resources.

Just a note, in future versions, I will drop the ES river API, and the JDBC
plugin will manage an internal state, where the number of execution cycles
can be configured.

Jörg

On Thu, Feb 12, 2015 at 5:18 PM, Abid Hussain hussain@novacom.mygbiz.com
wrote:

So I tried the oneshot strategy with no success. The river is being rerun
after restart of cluster.

Am Donnerstag, 12. Februar 2015 15:22:27 UTC+1 schrieb Abid Hussain:

Hi all,

we run a jdbc river once per night for a complete recreation of our index.

The river - once it has been created - will run again after a restart of
elasticsearch cluster (single node cluster). But what we try to achieve is
a one shot river, which isn't being re-run after restart of cluster.

Naturally we can trigger an event (e.g. as a cronjob) which - after the
estimated end of river run - deletes the river again. But this results in
additional efforts.

The easiest strategy may be do delete the river right away after creating
it. But I suppose in this case the running river would be stopped...?

My question is: what is the best way to create a one shot river which is
not being re-run after restart of cluster?

I noticed the oneshot strategy but didn't find any documentation in
https://github.com/jprante/elasticsearch-river-jdbc/wiki/Strategies.

Any help would be appreciated.

Regards,

Abid

--
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/dea5b9f2-36a5-4f09-b2c0-ca44157a4d9c%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/dea5b9f2-36a5-4f09-b2c0-ca44157a4d9c%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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/CAKdsXoHD2VbNz78YwzLK6iETXjYGCEtXyiwYmhBrXr2AsGvr0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.