Precise shard routing, remote document specific nodes

Elastic Stack Elasticsearch
1

Hi guys!

One of my clients wants to have local nodes of the index. Just in case our
server go down.

Let me explain: say I have an index, call it "documents", spread of 20
shards, 5 nodes.
I want 2 of the nodes to be local to my client, and the remaining 3 local
to me. But.
I want their node to only contain their documents, and the remaining 3 to
contain all the other clients.

Is that possible without having to push the documents on 2 different
clusters (2 + 3)?
I thought about explicit shard routing, but I'm not sure how to
specifically route on the shard
(as I believe routing is done via hashing then modding on the complete
keyspace, which would
be "random", but also guarantees no hotspots on the cluster).

How would you do that?
Steeve

2

I am not sure I completely follow the question, but it does not seem like
routing would help much here..., how about a local index and a remote index?

On Thu, May 24, 2012 at 4:37 PM, Steeve Morin steeve.morin@gmail.comwrote:

Hi guys!

One of my clients wants to have local nodes of the index. Just in case our
server go down.

Let me explain: say I have an index, call it "documents", spread of 20
shards, 5 nodes.
I want 2 of the nodes to be local to my client, and the remaining 3 local
to me. But.
I want their node to only contain their documents, and the remaining 3 to
contain all the other clients.

Is that possible without having to push the documents on 2 different
clusters (2 + 3)?
I thought about explicit shard routing, but I'm not sure how to
specifically route on the shard
(as I believe routing is done via hashing then modding on the complete
keyspace, which would
be "random", but also guarantees no hotspots on the cluster).

How would you do that?
Steeve

3

Hello,

I have a similar requirement for some documents to be stored only on the
local node.

A local index as @Kimchy suggests sounds like a good solution -- but how do
you create one?

Thank you,

  • Daniel

--
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/d622db36-1979-4662-8c6a-847040a87207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.