I have 2 nodes and I created a new index and given this routing rule. Node
1 has "node.group1 : group1" set in yaml file and Node 2 has "node.group1 :
group2" set in the file. However, when I write data it still is getting
writen to both the nodes. I just want it to go to only Node 2. Can I get
some suggestions on why this might be happening?
I have 2 nodes and I created a new index and given this routing rule. Node
1 has "node.group1 : group1" set in yaml file and Node 2 has "node.group1 :
group2" set in the file. However, when I write data it still is getting
writen to both the nodes. I just want it to go to only Node 2. Can I get
some suggestions on why this might be happening?
I have 2 nodes and I created a new index and given this routing rule.
Node 1 has "node.group1 : group1" set in yaml file and Node 2 has
"node.group1 : group2" set in the file. However, when I write data it still
is getting writen to both the nodes. I just want it to go to only Node 2.
Can I get some suggestions on why this might be happening?
I have 2 nodes and I created a new index and given this routing rule.
Node 1 has "node.group1 : group1" set in yaml file and Node 2 has
"node.group1 : group2" set in the file. However, when I write data it still
is getting writen to both the nodes. I just want it to go to only Node 2.
Can I get some suggestions on why this might be happening?
if you could include a fully fledged example of what you did, including
your configuration changes and all the curl commands you executed, this
would help people to debug your problem, see
I have 2 nodes and I created a new index and given this routing rule.
Node 1 has "node.group1 : group1" set in yaml file and Node 2 has
"node.group1 : group2" set in the file. However, when I write data it still
is getting writen to both the nodes. I just want it to go to only Node 2.
Can I get some suggestions on why this might be happening?
I added to the yaml file for node .86. I only want this index to be stored
on .86 node but it also is getting stored in .242 node. I have 2 nodes so
far.
node.group1: group2
Then I added this setting:
curl -XPUT 10.80.140.86:9200/test4/_settings -d '{
"index.routing.allocation.include.group1" : "group2",
"index.routing.allocation.exclude.group1" : "group1"
}'
Head shows this for 2 nodes:
{
name: 10.80.140.242
transport_address: inet[/10.80.140.242:9300]
version: 0.90.6
http_address: inet[/10.80.140.242:9200]
attributes: {
group1: group1
}
}
{
name: 10.80.140.86
transport_address: inet[/10.80.140.86:9300]
version: 0.90.6
http_address: inet[/10.80.140.86:9200]
attributes: {
group1: group2
}
}
{
state: open
settings: {
index.number_of_replicas: 1
index.number_of_shards: 5
index.version.created: 900699
index.uuid: Bqd1gRznTl6U5IUFDevLqA
index.routing.allocation.include.group1: group2
index.routing.allocation.exclude.group1: group1
}
mappings: { }
aliases:
}
On Fri, Nov 22, 2013 at 10:10 PM, Alexander Reelsen alr@spinscale.dewrote:
I have 2 nodes and I created a new index and given this routing rule.
Node 1 has "node.group1 : group1" set in yaml file and Node 2 has
"node.group1 : group2" set in the file. However, when I write data it still
is getting writen to both the nodes. I just want it to go to only Node 2.
Can I get some suggestions on why this might be happening?
I added to the yaml file for node .86. I only want this index to be stored
on .86 node but it also is getting stored in .242 node. I have 2 nodes so
far.
node.group1: group2
Then I added this setting:
curl -XPUT 10.80.140.86:9200/test4/_settings -d '{
"index.routing.allocation.include.group1" : "group2",
"index.routing.allocation.exclude.group1" : "group1"
}'
Head shows this for 2 nodes:
{
name: 10.80.140.242
transport_address: inet[/10.80.140.242:9300]
version: 0.90.6
http_address: inet[/10.80.140.242:9200]
attributes: {
group1: group1
}
}
{
name: 10.80.140.86
transport_address: inet[/10.80.140.86:9300]
version: 0.90.6
http_address: inet[/10.80.140.86:9200]
attributes: {
group1: group2
}
}
{
state: open
settings: {
index.number_of_replicas: 1
index.number_of_shards: 5
index.version.created: 900699
index.uuid: Bqd1gRznTl6U5IUFDevLqA
index.routing.allocation.include.group1: group2
index.routing.allocation.exclude.group1: group1
}
mappings: { }
aliases:
}
On Fri, Nov 22, 2013 at 10:10 PM, Alexander Reelsen alr@spinscale.dewrote:
I have 2 nodes and I created a new index and given this routing rule.
Node 1 has "node.group1 : group1" set in yaml file and Node 2 has
"node.group1 : group2" set in the file. However, when I write data it still
is getting writen to both the nodes. I just want it to go to only Node 2.
Can I get some suggestions on why this might be happening?
Wow this is really weird . Actually I was also facing the same problem some
time back. But it got solved by playing around with ira.exclude.* and
ira.require.* setting. Here are some things you can try. I can't guarantee
that it will work.
I think you should just have index.routing.allocation.exclude.group1:
group1 in the settings of the test4 index. Also see if you can set the
value of the node attribute (key) to something else than group1.
Also, are you using any cluster routing awareness setting in your
elasticsearch.yml file ?
Let me know how it goes!
Cheers!
On Wednesday, November 27, 2013 4:01:02 PM UTC-8, Mo wrote:
I am still looking for suggestions.
On Sun, Nov 24, 2013 at 7:01 PM, Mohit Anchlia <mohita...@gmail.com<javascript:>
wrote:
I added to the yaml file for node .86. I only want this index to be
stored on .86 node but it also is getting stored in .242 node. I have 2
nodes so far.
node.group1: group2
Then I added this setting:
curl -XPUT 10.80.140.86:9200/test4/_settings -d '{
"index.routing.allocation.include.group1" : "group2",
"index.routing.allocation.exclude.group1" : "group1"
}'
Head shows this for 2 nodes:
{
name: 10.80.140.242
transport_address: inet[/10.80.140.242:9300]
version: 0.90.6
http_address: inet[/10.80.140.242:9200]
attributes: {
group1: group1
}
}
{
name: 10.80.140.86
transport_address: inet[/10.80.140.86:9300]
version: 0.90.6
http_address: inet[/10.80.140.86:9200]
attributes: {
group1: group2
}
}
{
state: open
settings: {
index.number_of_replicas: 1
index.number_of_shards: 5
index.version.created: 900699
index.uuid: Bqd1gRznTl6U5IUFDevLqA
index.routing.allocation.include.group1: group2
index.routing.allocation.exclude.group1: group1
}
mappings: { }
aliases:
}
On Fri, Nov 22, 2013 at 10:10 PM, Alexander Reelsen <a...@spinscale.de<javascript:>
I have 2 nodes and I created a new index and given this routing
rule. Node 1 has "node.group1 : group1" set in yaml file and Node 2 has
"node.group1 : group2" set in the file. However, when I write data it still
is getting writen to both the nodes. I just want it to go to only Node 2.
Can I get some suggestions on why this might be happening?
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.