Alias across tribe node clusters?


(Nelson Jeppesen) #1

I want to scale ES between data centers for use with logstash and tribe
node(s) sound like a great solution to this. One problem is that I'm not
sure how aliases work across clusters.

Here's the general idea. two clusters and an alias index on the tribe
cluster. Can you do this? Thanks for your help!

tribe node:
alias: logstash_yyyy.mm.dd
members:
logstash_datacenter2_yyyy.mm.dd (es cluster 1)
logstash_datacenter1_yyyy.mm.dd (es cluster 2)

--
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/9a58828c-20b9-4ff3-9520-341b81e8e914%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Nelson Jeppesen) #2

Can anyone help me or know of a workaround? I've tried creating an alias on
a tribe node and I get the following on ES1.0:

curl -XPOST 'http://localhost:9200/_aliases' -d '

{
"actions" : [
{ "add" : { "index" : "1", "alias" : "alias1" } }
]
}'
{"error":"MasterNotDiscoveredException[waited for [30s]]","status":503}

On Wednesday, February 12, 2014 2:41:26 PM UTC-8, Nelson Jeppesen wrote:

I want to scale ES between data centers for use with logstash and tribe
node(s) sound like a great solution to this. One problem is that I'm not
sure how aliases work across clusters.

Here's the general idea. two clusters and an alias index on the tribe
cluster. Can you do this? Thanks for your help!

tribe node:
alias: logstash_yyyy.mm.dd
members:
logstash_datacenter2_yyyy.mm.dd (es cluster 1)
logstash_datacenter1_yyyy.mm.dd (es cluster 2)

--
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/a20708d6-9e99-4788-9a2b-a96d0dad71a7%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Luca Cavanna) #3

You can read and write data using the tribe node, but you cannot execute
master level write operations. Those are all the operations that modify the
cluster state, something that's done only by the master node.
As aliases are part of the cluster state, modifying them means modifying
the cluster state, which is not possible using the tribe node. This is
stated in the
docs: http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-tribe.html
.

Cheers
Luca

On Wednesday, February 19, 2014 11:39:37 PM UTC+1, Nelson Jeppesen wrote:

Can anyone help me or know of a workaround? I've tried creating an alias
on a tribe node and I get the following on ES1.0:

curl -XPOST 'http://localhost:9200/_aliases' -d '

{
"actions" : [
{ "add" : { "index" : "1", "alias" : "alias1" } }
]
}'
{"error":"MasterNotDiscoveredException[waited for [30s]]","status":503}

On Wednesday, February 12, 2014 2:41:26 PM UTC-8, Nelson Jeppesen wrote:

I want to scale ES between data centers for use with logstash and tribe
node(s) sound like a great solution to this. One problem is that I'm not
sure how aliases work across clusters.

Here's the general idea. two clusters and an alias index on the tribe
cluster. Can you do this? Thanks for your help!

tribe node:
alias: logstash_yyyy.mm.dd
members:
logstash_datacenter2_yyyy.mm.dd (es cluster 1)
logstash_datacenter1_yyyy.mm.dd (es cluster 2)

--
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/7c7ed271-b1cc-4b81-80d7-c4114f7f0474%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #4