ElasticSearch Multi Data Center replication

Elastic Stack Elasticsearch
1

Hi,

Is there a solution for this ? Could you recommend some production proven?
Thank you
Vladi

--
This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of the
addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.

--
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/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Use the snapshot / restore API, unless you care for latency then look at
implementing a daemon tool to do that. You should try to keep them decoupled

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Thu, Apr 2, 2015 at 2:48 PM, Vladi Feigin vladif@liveperson.com wrote:

Hi,

Is there a solution for this ? Could you recommend some production proven?
Thank you
Vladi

This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of
the addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.

--
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/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%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/CAHTr4ZtAMWcLLtJP0WTgFkofBBa04wW%2Buypx456BnQYLmVwmvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

Thank you Itamar,
Can you describe the process with the more details?
Is it something like that:

  1. Extract a snapshot in cluster_source with snapshot API
  2. Copy it to target cluster
  3. Restore it in the target cluster with restore API

All this wrap in the two daemon jobs , one for snapshot (running in the
source cluster) and other for restoring running in the target cluster?
Thank you,
Vladi

On Thu, Apr 2, 2015 at 2:58 PM, Itamar Syn-Hershko itamar@code972.com
wrote:

Use the snapshot / restore API, unless you care for latency then look at
implementing a daemon tool to do that. You should try to keep them decoupled

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Thu, Apr 2, 2015 at 2:48 PM, Vladi Feigin vladif@liveperson.com
wrote:

Hi,

Is there a solution for this ? Could you recommend some production proven?
Thank you
Vladi

This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of
the addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.

--
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/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/iRMQb8vVG_w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtAMWcLLtJP0WTgFkofBBa04wW%2Buypx456BnQYLmVwmvw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtAMWcLLtJP0WTgFkofBBa04wW%2Buypx456BnQYLmVwmvw%40mail.gmail.com?utm_medium=email&utm_source=footer
.

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

--
This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of the
addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.

--
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/CACvWdiqR%2B9trJZ6gv2fbf0FiyEsL_C%2BazrE7D4V0L7aw3T%3D_Sg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

4

If you don't want to snapshot+restore then use your code to write to each
cluster.

On 2 April 2015 at 23:06, Vladi Feigin vladif@liveperson.com wrote:

Thank you Itamar,
Can you describe the process with the more details?
Is it something like that:

  1. Extract a snapshot in cluster_source with snapshot API
  2. Copy it to target cluster
  3. Restore it in the target cluster with restore API

All this wrap in the two daemon jobs , one for snapshot (running in the
source cluster) and other for restoring running in the target cluster?
Thank you,
Vladi

On Thu, Apr 2, 2015 at 2:58 PM, Itamar Syn-Hershko itamar@code972.com
wrote:

Use the snapshot / restore API, unless you care for latency then look at
implementing a daemon tool to do that. You should try to keep them decoupled

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Thu, Apr 2, 2015 at 2:48 PM, Vladi Feigin vladif@liveperson.com
wrote:

Hi,

Is there a solution for this ? Could you recommend some production
proven?
Thank you
Vladi

This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of
the addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.

--
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/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/bb6ef682-5a94-4f2e-9cfb-345a9c31ffa7%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/iRMQb8vVG_w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtAMWcLLtJP0WTgFkofBBa04wW%2Buypx456BnQYLmVwmvw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtAMWcLLtJP0WTgFkofBBa04wW%2Buypx456BnQYLmVwmvw%40mail.gmail.com?utm_medium=email&utm_source=footer
.

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

This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of
the addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.

--
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/CACvWdiqR%2B9trJZ6gv2fbf0FiyEsL_C%2BazrE7D4V0L7aw3T%3D_Sg%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CACvWdiqR%2B9trJZ6gv2fbf0FiyEsL_C%2BazrE7D4V0L7aw3T%3D_Sg%40mail.gmail.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/CAEYi1X8QtEo69QOh2JvpTMawmTK%2Bp%3DkaMqZxGjTP7wRAoKfH9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.