Hello,
I'm joining this topic because I'm having the same king of issue on my
system.
I'm trying to build a log indexation engine based on elastic search and I
have:
ES master node
ES slave node
logstash
logstash outputs to ES slave node:
output {
elasticsearch {
bind_host => "10.30.19.87"
cluster => "ubiqube"
}
}
the issue is that every time a new logstash index is created, it is
unassigned but appart from this it looks fine.
I did the test with curl -X PUT localhost:9200/mytest
and this new index is also created as unassigned.
with the "head" plugin I can see each shard status:
{
state: UNASSIGNED
primary: false
node: null
relocating_node: null
shard: 3
index: mytest
}
Any idea?
logstash and ES version V1-1-1
Antoine Brun
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Unassigned-shards-v2-tp4046370p4056142.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/1400583879699-4056142.post%40n3.nabble.com.
For more options, visit https://groups.google.com/d/optout.
