Thanks for your reply. I set the node.rack to rack_one on all the nodes as a test. In ElasticHQ, on the right it shows no indices. It is empty. In my master, I see that the nodes are identifying with rack_one (all of them).
Any other clues? Thanks Brian On Thursday, May 22, 2014 5:10:25 PM UTC-4, Mark Walkom wrote: > > It does create an index, it says so in the log - [logstash-2014.05.22] > creating index - it's jut not assigning things. > > You've set routing.allocation.awareness.attribute, but have you set the > node value, ie node.rack? > See > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-cluster.html#allocation-awareness > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com <javascript:> > web: www.campaignmonitor.com > > > On 23 May 2014 02:22, Brian Wilkins <bwil...@gmail.com <javascript:>>wrote: > >> I have five nodes : Two Master Nodes, One Balancer Node, One Workhorse >> Node, and One Coordinator Node. >> >> I am shipping events from logstash, redis, to elasticsearch. >> >> At the moment, my cluster is RED. The shards are created but no index is >> created. I used to get an index like logstash.2014-05-22, but not anymore. >> >> I deleted all my data, Cluster health goes GREEN. >> >> However, as soon as data is sent from logstash -> redis -> elasticsearch, >> my cluster health goes RED. I end up with unassigned shards. In my >> /var/log/elasticsearch/logstash.log on my master, I see this in the log: >> >> [2014-05-22 12:03:20,599][INFO ][cluster.metadata ] [Bora] >> [logstash-2014.05.22] creating index, cause [auto(bulk api)], shards >> [5]/[1], mappings [_default_] >> >> On my master, this is the configuration: >> >> cluster: >> name: logstash >> routing: >> allocation: >> awareness: >> attributes: rack >> node: >> data: true >> master: true >> >> curl -XGET 'http://localhost:9200/_cluster/health?pretty=true' >> { >> "cluster_name" : "logstash", >> "status" : "red", >> "timed_out" : false, >> "number_of_nodes" : 5, >> "number_of_data_nodes" : 3, >> "active_primary_shards" : 0, >> "active_shards" : 0, >> "relocating_shards" : 0, >> "initializing_shards" : 0, >> "unassigned_shards" : 10 >> } >> >> Is there an incorrect setting? I also installed ElasticHQ. It tells me >> the same information. >> >> Brian >> >> -- >> 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:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/03c5974b-ae50-4f1c-9ba3-4ef94b564323%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/03c5974b-ae50-4f1c-9ba3-4ef94b564323%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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5bd4c3d5-3be5-44ef-a8a6-5dba6876130c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
